moduliths VS spring-modulith-sample

Even since the microservices craze started, some cooler heads have prevailed. In particular, Oliver Drotbohm, a developer on the Spring framework, has been a long-time proponent of the moduliths alternative. The idea is to keep a monolith but design it around modules.

Not sure if that will be complete example but for coding I would go trough Spring dev members in Github: - Olivier Gierke : https://github.com/moduliths/moduliths (Modulith) - Rossen Stoyanchev : https://github.com/rstoyanchev - Dave Syer : https://github.com/dsyer

Conceptually, there a lot of similarities to Moduliths. Moduliths helps you to build modular Spring Boot applications which are preferred to be deployed as a single unit. Like archifacts Moduliths uses ArchUnit to enforce certain architectural constraints and - based on some rules - it's able to identify the application's building blocks.

Moduliths - a Spring Boot extension that allows to structure your application into logical modules, test those individually and derive high-level documentation for the structure created.

I've created a sample app to play with: it emulates the home page of an online shop. The home page is generated server-side with Thymeleaf and displays catalog items and a newsfeed. The latter is also accessible via an HTTP API for client-side calls (that I was too lazy to code). Items are displayed with a price, thus requiring a pricing service.