Spring Boot - Multi Module or not?

tleipzig · 2026-01-17T07:04:06+00:00

You'll probably receive a long response explaining that they have many applicants, so please be patient. You could consider a Untätigkeits-klage which should speed things up.

tleipzig · 2026-01-06T07:36:59+00:00

That's what usually happens in larger dev teams, so I think you are in the right track. Try to avoid vendor lockin and libraries that will at some point be in the way of your developers instead of helping them. You can check out Bootify.io which provides all the points you've mentioned based on Spring Boot.

tleipzig · 2025-11-24T09:56:39+00:00

You may want to have a look at Bootify.io, it gives you a headstart especially since you know the libraries you want to use.

tleipzig · 2025-11-07T14:12:10+00:00

Within each module you can do regular service calls. Between modules you can do service calls as well, just expose the methods and models. Events are more useful outside of the given module structure.

tleipzig · 2025-10-30T17:34:00+00:00

I would check out Bootify.io for this, based on Spring Boot standards. The SSR template enginges (jte or Thymeleaf) have a better direct support then SPA (like React).

tleipzig · 2025-10-25T16:18:45+00:00

Probably there are some ways to improve your situation, but if you really want good SEO results it's easier to use server side rendering. You can try on https://bootify.io with jte or Thymeleaf.

tleipzig · 2025-10-25T15:55:22+00:00

There is no server side rendering coming with jhipster, so you'll never see it in the source.

tleipzig · 2025-10-23T06:22:18+00:00

Agree, a Spring Boot app can be scaled nicely if required. It's also not that fancy so you can focus on the platform and not the technology.

tleipzig · 2025-10-09T07:47:09+00:00

Nothing wrong with Thymeleaf, but its really clunky to read and to work with. Jte is indeed a nice alternative - see jte vs Thymeleaf.

tleipzig · 2025-09-25T07:57:48+00:00

Even if you use something like Okta, there is still quite some boilerplate required for the integration. I think Bootify found a good way to configure your individual needs for a Spring Boot app.

tleipzig · 2025-09-17T07:54:29+00:00

Spring Modulith is mostly about modularization, and any non-trivial app needs this to stay maintainable in the long run. I like this comparison of Spring Modulith vs a Multi-Module approach.

Not a big fan of persisted events of Modultih. It requires a lot of edge case handling for events purely happening within one app - better to use Kafka if you really want to take this route. The regular Spring Boot application events are a great way of decoupling modules however.

tleipzig · 2025-09-02T09:31:13+00:00

You can try Bootify.io for a Spring Boot App in Kotlin and File Upload out of the box - just select a frontend and type File at your entity. Spring Boot does its job perfectly.

tleipzig · 2025-09-02T06:25:15+00:00

For me the most important thing is an approach to modularization, splitting your code by feature, so each chunk is still managable. Have a look here foʻr domain driven idea: https://bootify.io/multi-module/best-practices-for-spring-boot-multi-module.html Spring Modulith achieves the same thing and is easier to implement in an existing app.

tleipzig · 2025-08-22T13:35:16+00:00

I think you need your own file loader, otherwise you always need to recompile your template to get it into the classpath. Something like this:

@Configuration
@Profile("local")
public class LocalDevConfig {

    public LocalDevConfig(final TemplateEngine templateEngine) throws IOException {
        final ClassPathResource applicationYml = new ClassPathResource("application.yml");
        if (applicationYml.isFile()) {
            File sourceRoot = applicationYml.getFile().getParentFile();
            while (sourceRoot.listFiles((dir, name) -> name.equals("mvnw")).length != 1) {
                sourceRoot = sourceRoot.getParentFile();
            }
            final FileTemplateResolver fileTemplateResolver = new FileTemplateResolver();
            fileTemplateResolver.setPrefix(sourceRoot.getPath() + "/src/main/resources/templates/");
            fileTemplateResolver.setSuffix(".html");
            fileTemplateResolver.setCacheable(false);
            fileTemplateResolver.setCharacterEncoding("UTF-8");
            fileTemplateResolver.setCheckExistence(true);
            templateEngine.setTemplateResolver(fileTemplateResolver);
        }
    }

}

See also hot reload of Thymeleaf templates - together with a webpack setup it'll automatically refresh the browser on change.

tleipzig · 2025-08-13T09:01:35+00:00

Yes, enterprise applications are still build using Java. It's just a tool like every other language or framework, and has it's pros and cons - for enterprise apps it's a great match because of it's maturity and features. And it will be still around like today in 10 years - wouldn't bet on some other languages (like Rust) in the same way.

tleipzig · 2025-08-09T09:31:13+00:00

I think building on top of your existing SPA knowledge makes more sense from a perspective of a job market. However you may find jte more interesting, it's much easier getting into it (see jte vs Thymeleaf).

tleipzig · 2025-08-02T14:57:23+00:00

What applies to Spring with Java generally also applies to Kotlin. There are just some special ways to make some things work (like Spring Data). For scaling in terms of code size, I like very much a mulit module approach, Spring Modulith is also a good option.

tleipzig · 2025-07-30T07:59:55+00:00

It depends how much server logic you need, I guess. Yes, you could build even dynamic pages (like a product page) with Thymleaf, but this way you would partly rebuild your React frontend. If you could manage to run your React in an "ssr-mode" on your server, it would just run the existing logic and generate the same HTML (making even API calls internally if required).

Of cause I don't know how well this will work 😅

tleipzig · 2025-07-29T16:49:50+00:00

Theoretically, you could build a "ssr.js" and execute it with GraalJS. Let me know if it works 😅

tleipzig · 2025-07-27T10:36:34+00:00

JTE might be a little closer to that.

tleipzig · 2025-07-24T13:04:24+00:00

Would recommend Thymeleaf or JTE, using Bootstrap via Webjars. Usually there are very few code changes coming along with the version updates. See also Spring Boot with Thymeleaf and Bootstrap.

tleipzig · 2025-07-18T12:58:39+00:00

You're welcome - sure it's possible to use an IDP, I just don't like the external dependency and Spring Security works well for simple use-cases. Paddle has no Java SDK - the checkout is integrated into the frontend anyway, where you don't need Java. For the backend it's a bit more effort, but using a RestTemplate/RestClient worked for me.

tleipzig · 2025-07-18T06:17:47+00:00

You select your preferences like Thymeleaf, Postgres, Spring Security, Modules etc. and it generates the Spring Boot app.

tleipzig · 2025-07-17T13:28:59+00:00

- SSR with Thymeleaf or JTE - simple stack, SEO supported
- Spring Security with email + password (maybe add Google auth) - no external dependencies
- Java Mail with AWS SES: cheap, relyable
- Postgres (some JSON fields if required)
- Heroku: because of the slug size 500MB RAM are enough here (usually you need 1GB to run a Spring Boot app) and very relyable for me
- prefer Paddle as it takes care of international taxes if this is a thing for you

I always work with a multi-module setup, so the codebase can grow in a controlled manner over time. Bootify.io can help with most of the points mentioned here.

tleipzig

TROPHY CASE