What problem does it solve? Deciding whether to adopt CQRS, whether to combine it with event sourcing, and how to balance consistency, availability, and scalability across read and write models is a recurring architecture challenge. This Skill provides a structured evaluation framework grounded in the CAP theorem so you can make defensible design decisions instead of guessing. ## Core Features & Use Cases - CAP-based evaluation axes: Explains why write models demand strong consistency while read models can accept eventual consistency, with concrete tradeoff tables. - Adoption decision flow: A step-by-step flowchart for choosing between simple CRUD, simple CQRS, and CQRS with event sourcing based on load characteristics and consistency requirements. - Review checklists: Ready-to-use checklists covering architecture rationale, consistency design, availability design, and scalability design for design reviews. - Use Case: When asked "should we adopt CQRS for our order system?", walk through the decision flow, assess whether eventual consistency is acceptable for each read model, and produce a documented recommendation. ## Quick Start Ask the AI to evaluate whether CQRS with event sourcing is appropriate for your system, describing your read/write load characteristics and consistency requirements.
