moduliths VS jmolecules

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.

Spring Modulith is the successor of Oliver Drotbohm's Moduliths project (with a trailing S). It uses both ArchUnit and jMolecules. At the time of this writing, it's experimental.

You could move towards modeling your code around DDD building blocks (like aggregates etc.) and declare those concepts in code explicitly using jMolecules types. There is a dedicated jMolecules Integrations ByteBuddy Plugin, that would then add the necessary boilerplate code and default mappings required by the expressed concept. This makes the code shown here a fully working JPA model. You can argue that the lack of JPA oddities is odd itself in the first place but I like the idea of expressing the architectural concept explicitly and the technology integration completely flowing from that.