.NET CQRS Pattern

Overview

CQRS separates read and write operations into different models, allowing optimization of each. This skill should be invoked when building scalable architectures that need different models for reads and writes, or complex business logic that benefits from separation.

Core Principles

• Separation: Commands (writes) and Queries (reads) use different models
• Optimization: Each side can be optimized independently
• Mediator Pattern: Use MediatR for decoupling handlers
• Explicit Intent: Operations are clearly commands or queries

Preparation Checklist

• Understand CQRS benefits and trade-offs
• Plan command and query boundaries
• Choose implementation approach (with/without MediatR)
• Define DTOs for responses