architecture-patterns

To separate domain logic from infrastructure during a monolith refactoring, apply Hexagonal Architecture and Domain-Driven Design patterns. This Skill provides practical templates to define ports and adapters, enforcing a strict separation of concerns between your core business rules and external infrastructure components.

Establishing backend architecture standards across teams requires codified patterns, explicit folder structures, and defined adapter responsibilities. This Skill supplies concrete templates for Clean Architecture and Domain-Driven Design to ensure consistent implementation and maintainable scalable software across your organization.

To define ports and adapters for scalable backend systems, you map your domain boundaries to interfaces (ports) and implement external integrations as separate components (adapters). This Skill codifies adapter responsibilities and port definitions to ensure clean separation of concerns.

You should use Domain-Driven Design patterns when designing complex backend systems that require strict separation of concerns and scalable architecture. This Skill helps you apply DDD alongside Hexagonal Architecture to map complex business domains into maintainable layered structures.

Yes, these backend architecture patterns apply to both designing new systems and refactoring monoliths. The Skill provides practical templates for Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to establish consistent architectural standards across teams for any backend context.