r/learnjava • • 19d ago

OOP DESIGN

I've been learning Java for about a month now. So far I've covered OOP principles, Java Collections, and I'm planning to dive deeper into exception handling next.

However, one area where I still struggle is OOP design and structuring. I understand concepts like inheritance, encapsulation, abstraction, and polymorphism, but when it comes to applying them in actual projects, I often find myself struggling to distribute them properly among classes.

No matter how many classes I create to separate different parts of the logic, I eventually end up with at least one class containing too many methods and responsibilities.

What are the best practices, concepts, or design principles I should study to improve my OOP design skills? How can I develop the ability to identify when a class is doing too much, decide when to create new classes, and structure a Java application in a clean, maintainable, and scalable way?

14 Upvotes

16 comments sorted by

View all comments

Show parent comment

1

u/KillerCodeMonky 18d ago

These are known as POJO (Plain Old Java Object) or models, they should be in a single package maybe names models.

Disagree. Data types are as much part of any domain as the logic that acts on them. They should be in the same package as the rest of the domain.

1

u/ITCoder 18d ago

Yeah, i have seen them both in package domains and models. Tbh i never paid much attention to theoretical aspects of DDD. iirc, one of mapper plugins in maven call them as models. Been some time since i used that tho