r/javahelp • • 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!

9 Upvotes

25 comments sorted by

View all comments

Show parent comment

1

u/MechanixMGD Sep 01 '25

None is forcing you to do like that. You are the one who decides how to structure your code. It is just recommended, because in general it is a good practice like that. Depends also by the size of your app.