spring-boot-modulith

Use Spring Modulith's @ApplicationModule annotation to declare module boundaries within your Spring Boot application. Each module contains a public API package and encapsulated internals, enforcing separation of concerns and preventing unwanted cross-module dependencies.

Implement event-driven communication using @ApplicationModuleListener to publish and handle events across modules. This decouples modules while maintaining consistency, enabling asynchronous cross-module workflows without direct dependencies.

Yes. Spring Modulith provides module verification that runs in CI/CD pipelines to detect architectural violations. It generates PlantUML documentation and ensures modules respect declared boundaries, catching violations early in development.

Spring Modulith supports event externalization to messaging systems like Kafka and AMQP. Configure event publication logs using JDBC-based storage, then route events to your chosen messaging infrastructure for distributed system integration.

Yes. Spring Modulith 2.0 is designed for Spring Boot 4 applications. It provides patterns and tooling specifically for building modular monoliths with modern Spring Boot architecture, including module configuration and event handling semantics.

Modules declare a public API package for external consumption and internal packages that remain encapsulated. This enforces module contracts, preventing other modules from depending on implementation details and maintaining clean architectural boundaries.