SpringBoot project structured with Clean Architecture enforced by Maven MultiModule with whipped cream (Automated Tests) and a cherry added on top (Code Quality Analysis).
Simple application (domain complexity) with hard architectural boundaries enforced by maven multimodule following Clean Architectural guidelines using Spring to make DI easy. In this CA, Spring framework is decoupled and required only in the external layers (api and datasources).
- Spring (easy DI setup (Spring IoC))
- SpringBoot (Quick Spring project setup)
- Maven MultiModule (Enforced Architectural Boundaries)
- Clean Architecture
Extras 1: This project features automated tests to demonstrate a way to do so in a clean architecture style with enforced boundaries. Since this is not a real-world application, the test suit doesn't go further than integration and unit tests.
- JUnit, Mockito and AssertJ
- Flyway
- H2 and Postgres
- Test Containers
Extras 2: This project also features automated code quality analysis by using:
- SonarQube
- GitHub Actions
Extras 3: RESTful API with Docs.
- RESTful API (HATEOAS)
- Documentation (Spring RestDocs + AsciiDoc + Pandoc & GitHub Actions)
Extras 4: Domain-Driven Design. Just a little bit to model this small project domain, even tho DDD is not recommended for small projects. This project stays just at the tip of the DDD iceberg. Check out the Project Domain.
- Domain PoC Planning
- Project Domain
- Project Architecture
- Setup and Configuration
- Contributing
- Getting help
- Be nice to everyone
- Customer
- Domain
- Entities
- UseCases
- Adapters
- Controllers
- External
- Datasources
- Apis
- Domain
- Product
- Order
