backend-java

Structure your Spring Boot backend using hexagonal architecture by separating Domain, Application, Infrastructure, and API layers. This Skill automates designing controllers, services, and repository adapters, enforcing dependency injection discipline and clean layer boundaries.

Yes, you can keep Spring annotations out of your Domain layer in Java. This Skill enforces hexagonal architecture guidelines that restrict Spring dependencies to the Infrastructure layer, keeping your Domain pure and framework-agnostic.

Implement structured logging and health checks in a Java backend by applying hexagonal architecture patterns. This Skill guides adding observability middleware across your Application and Infrastructure layers to ensure consistent monitoring.

Use Java records for DTOs and ApiResponse envelopes in Spring Boot to conform to modern design guidelines. This Skill automatically scaffolds API layer components using records for data transfer and standardized envelopes for API responses.

Yes, this hexagonal architecture approach works for scaffolding dependency injection configurations. It targets DI setup across adapters and middleware, ensuring proper wiring between Application ports and Infrastructure adapters in Spring Boot.

Use hexagonal architecture for a Java Spring Boot application to achieve clean separation of concerns between business logic and external interfaces. This approach isolates your Domain core, making components easier to test, maintain, and swap.