moduliths VS ArchUnit-Examples

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.

The problem I've had with these tests is that the run time is abysmal, meaning they only really get run as part of CI and devs complain that they fail too late in the process

Also, I'm on mobile so apologies for the badly formatted code - original can be found here: https://github.com/TNG/ArchUnit-Examples/blob/main/example-j...

Since I have no real project in the open, unfortunatly not. But the ArchUnit example repo is quite extensive: https://github.com/TNG/ArchUnit-Examples

Here are some ArchUnit examples if you're new to this.

Other examples