Spring Modulith - Spring for the Architecturally Curious Developer by Oliver Drotbohm

The architecture and design of an application significantly influences its maintainability, testability, and quality in general. Spring has always been a versatile tool that supports architects in implementing the practices and patterns that have emerged to align technical building blocks in their code bases with domain concepts and boundaries. It lets developers build applications that clearly reflect architectural ideas and that are ultimately more amendable and maintainable. Key aspects of that are code organization for encapsulation, the Spring bean relationship arrangement, and how to use domain events to decouple logically individual parts of the application even within a singular artifact.
This talk discusses those patterns and approaches to introduce libraries, such as jMolecules and Moduliths to, in turn, show how they uniquely position Spring developers to build better structured, more maintainable applications.

[@BerndGoetz]

Great presentation - clear and crisp! Until recently, we (as in my teams in my professional context) didn't really care about internal application architectures, that's why so many big balls of mud were created. I really like the way that Spring Modulith creates a great basis to have educated discussions about internal architectures. Moreover, making events a first class citizen in this setup even further increases clarity and quality of more complex applications!

[@bahadiryagan]

I'm sold!

[@keletsoa.botsalano4531]

Seconded

[@balazsklezli5702]

This is pretty cool!

[@adambickford8720]

I wonder how hard it is to convert that messaging to an external one like SQS and carve off the service into its own thing?

[@leassisbr]

There is examples in their GitHub. But it's not hard