software-architecture-patterns

Architecture patterns like Hexagonal, CQRS, and Event Sourcing are compared through clear explanations of trade-offs and context examples. Hexagonal isolates domain logic, CQRS separates read and write models, and Event Sourcing persists state changes as an event sequence.

To write an Architecture Decision Record, compare architectural styles like Microservices and Layered systems using this Skill's reference files. It provides trade-off analysis and context examples to support architectural decision-making during system design sessions.

Use CQRS and Event Sourcing when you need scalable read/write separation and a complete audit trail of state changes. This Skill offers practical guidance on applying these architecture patterns, including their specific trade-offs and real-world context examples for system design.

Yes, this architecture reference covers fundamental styles including Event-Driven, Pipeline, Microkernel, SOA, and Microservices. It consolidates these styles alongside patterns like MVC and Hexagonal to support design discussions and architecture evaluations.

Event Sourcing introduces eventual consistency and complex event replay challenges during architectural design. This Skill outlines these trade-offs alongside other architecture patterns, helping teams evaluate when the approach suits their specific system design context.

Start applying architectural patterns by reading the handbook files in the references directory, which provide quick-start templates and context. These references guide teams through architecture reviews and applying styles like Hexagonal and MVC to real-world system design challenges.