Architecture Signals
One deployable application, separate Maven modules, ArchUnit boundary tests, and no fake microservice split.
Backend portfolio project
A production-minded backend showcase focused on clear module boundaries, pragmatic CQRS, internal Spring events, Flyway migrations, automated tests, generated API documentation, coverage, and CI-published documentation.
One deployable Spring Boot application. Separate Maven modules own separate business capabilities. Cross-module communication stays explicit through application services and Spring events.
One deployable application, separate Maven modules, ArchUnit boundary tests, and no fake microservice split.
Flyway migrations, Hibernate validation, Docker-backed integration tests, and idempotent order placement.
Architecture docs, ADRs, business flow, trade-offs, JavaDoc, coverage, and HTML test reports are published from CI.
This landing page, Markdown documentation, generated OpenAPI JSON, Swagger UI, JavaDoc, JaCoCo coverage, and HTML test reports.
GitHub Pages is static hosting. It does not run Spring Boot, PostgreSQL, Redis, background workers, or backend services.
Start PostgreSQL and Redis, then run the Spring Boot application from the executable module.
docker compose up -d
mvn -pl ecommerce-app -am spring-boot:run
mvn clean verify
The repository proves architecture and runtime behavior through tests, generated reports, and CI-published documentation.