architecture-patterns

Apply domain-driven design by outlining your domain, choosing an architecture pattern, and mapping interfaces and boundaries. This approach defines clear layers and domain modeling guidelines to improve maintainability and testability for new backend services.

Clean architecture and hexagonal architecture both separate domain logic from infrastructure using defined layers and ports and adapters. This Skill provides practical playbooks to help teams choose and apply the appropriate pattern based on their specific domain boundaries.

Refactor a monolith using ports and adapters by defining clear module boundaries and dependencies to separate domain logic from external interfaces. This Skill provides structured approaches and templates to accelerate aligning teams around these domain boundaries.

These architecture patterns apply to scaling existing backend systems by standardizing practices for maintainability and testability. You can use the provided templates to map interfaces and align domain boundaries during system refactoring.

Domain-driven design may be unnecessary for simple backend systems without complex domain logic. If your service requires minimal domain modeling or has limited scalability requirements, the overhead of defining bounded contexts and ports and adapters might not be justified.