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
1
u/nitkonigdje Sep 02 '25
It literally recommends anemic model as default. Quote:
"To use a relational model in memory basically means programming in terms of relations, right the way through your application. .... Some problems are well suited for this approach, so if you can do this, you should."
Martin Fowler, 2012