architecture-patterns

Clean architecture structures backend software into independent, cohesive layers, separating business rules from frameworks and UI to improve testability and flexibility. This skill provides guidance on layering and defining boundaries to achieve this separation.

Hexagonal architecture uses ports and adapters to enable easy swapping of infrastructure, ensuring core logic remains framework-agnostic. This skill provides practical guidance and example directory structures for refactoring existing monoliths using this approach.

Domain-Driven Design aligns models with business domains by defining bounded contexts and using strategic and tactical patterns to manage complexity. This skill guides mapping your domain and implementing core business logic in a framework-agnostic domain layer.

Bounded contexts and strategic patterns are needed when designing or refactoring complex backends to manage business domain complexity. This skill helps software engineering teams align models with business domains and define clear architectural boundaries.

Yes, this approach provides example directory structures and practical guidance for applying architectural patterns in new projects. You can map your domain, define ports and adapters, and implement core business logic using these templates.

Separating business rules from infrastructure improves testability by ensuring core logic remains framework-agnostic and infrastructure can be easily swapped. This skill provides patterns like clean and hexagonal architecture to structure software into independent, cohesive layers.