Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have been tasked with developing a web application that allows users to search for a client and invoke one of a handful of services that will ultimately generate a database query with user provided parameters and generate a report.

I am familiar with spring boot and spring MVC for smaller projects (example tutorials of blog building and online stores and such). What i am curious to know is how to structure the code beyond just using the MVC pattern. My initial plan is to create a sub module for each object like users, each report type (though they might want to share the same view), clients, and other things.

After doing some searching, i can't really find any examples of this way of breaking up the code. Maybe it that is because its not a good approach? IT just seems like a better way to separate responsibilities and each report will have different db credentials and properties so it makes sense in my mind.

Beyond MVC, is this a worthwhile approach for a organizing the code?

share|improve this question
2  
Questions that include words like "good" and "worthwhile" are inherently unanswerable. We don't know what those words mean to you specifically. State your specific requirements instead. – Robert Harvey Sep 2 at 23:04

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.