How xsreality/spring-modulith-with-ddd works
Project type and purpose
• This is a backend-only “modular monolith” built with Spring Boot, Spring Modulith and Domain-Driven Design.
• Purpose: manage library operations (catalog management, holds & checkouts) with OAuth2 security via Keycloak.
File structure
• Top-level modules (bounded contexts) under src/main/java/example:
• catalog – book catalog management
• borrow – hold & checkout workflows
• useraccount – shared security integration (JWT conversion, argument resolvers)
• Each module follows a Hexagonal/Docker-style layering:
• application – service APIs (use-case layer)
• domain – core entities & repositories (domain layer)
• infrastructure / ui / web – REST controllers (interface adapters)
• Root configs: LibraryApplication.java, LibraryWebSecurityConfiguration, Spring Modulith annotations for module partitioning.
• application.yaml, Maven (pom.xml), Docker Compose + Keycloak realm JSON.
README for additional insights
• Explicit mention of Spring Modulith modularization & eventual consistency.
• OAuth2 flows via Keycloak (external Authorization server).
• Single Docker Compose stack: application + Keycloak.
• Database interactions via Spring Data JPA (SQL scripts under src/test/resources).