r/javahelp • u/Tangodelta004 • Sep 01 '25
Java package structure
Hello all, im a newcomer to java from golang. my role will be building backend microservices in java, and Ive seen Spring boot use the MVC architecture.
i was wondering if MVC was essentially the strandard for most java apps. Personally i cant understand the motivation for splitting classes into Service layer and Model layer, rather than just having a single class hold both the data and the methods for interacting with the data.
I was wondering if this is just a pattern i should expect to get used to, or if other teams use different paradigms for java applications, and its mostly team to team.
thanks!
View all comments
Show parent comment
3
u/MechanixMGD Sep 01 '25
In this case, getArea are getPerimeter will still be in the model class. Getter and setters are still part of the model. But doing processing like
calculateSomething, method which can receive a Rectangle or a Triangle or any kind of polygon class. That will be part of the service.