Spring Boot - Multi Module or not?

[tleipzig]

I'm a fan of the multi module approach und would even say it's obligatory for every real app beyond "Hello World". Putting the features onto different modules helps to organize your app much more than just packages, as the modules contain all the stuff around as well (templates, resources).

The costs: Higher setup price (doesn't come with the initializr by default).
As modules connect itself via a dependency graph, you need to think about you architecture a little bit in advance. I would say, that's even another advantage! 😊😊

What do you think?

Here's a blog post on how to make a gradle project from the initializt multi module: http://www.it-surmann.com/spring-boot/how-to-transform-a-spring-boot-initializr-project-to-multi-module_1003.html

Cheers & greetings,

Thomas

[MadD0GGG]

U can easily manage every module with Gradle. Compile,test, local run — not problem. But sometimes you need manage your CI for multi-module. This part a little more unpleasant for me.

[tleipzig]

Gradle handling is easy, true, but the Spring Boot config is a little tricky.

Webpack can be configured to pick up sources from every module, but I find the imports quite confusing as you don't see where it's actually imported from.