architecture-patterns

To select an architecture pattern, identify your project's primary challenges like scalability, testability, or deployment strategy. This Skill provides guided decision-making criteria and tradeoff documentation to help you choose between Layered, Hexagonal, CQRS, and Event Sourcing architectures.

Use hexagonal architecture over layered architecture when clear boundary definitions and testability are critical. This Skill documents the specific tradeoffs and selection criteria to help you decide if hexagonal's adapter flexibility outweighs layered architecture's simplicity for your context.

Applying CQRS and event sourcing to distributed microservices involves defining clear boundaries for command and query separation. This Skill provides practical examples and use-case templates to guide design decisions, governance, and evolution for distributed systems.

Yes, the architecture pattern selection process works for simple monoliths. This Skill explicitly covers projects ranging from simple monoliths to distributed microservices, ensuring you can validate architecture choices across different scales using the provided verification checklist.

You validate architecture choices by applying the provided verification checklist to confirm pattern fit. This Skill satisfies requirements for documented trade-offs, clear boundary definitions, and integration references to external catalogs to concretely validate your architectural decisions.