Adventures in .NET What is Command Query Responsibility Segregation (CQRS) with Derek Comartin - .NET 213
9 snips
Jan 7, 2025 Derek Comartin, a developer at a Canadian transportation software startup, dives into the intricacies of Command Query Responsibility Segregation (CQRS). He outlines its benefits and potential downsides while sharing real-world applications. The discussion simplifies CQRS and domain-driven design, making it accessible to the audience. Derek also addresses the relationship between CQRS and event sourcing, emphasizing the importance of separating read and write operations. Plus, he shares personal favorites in media and activities, keeping the conversation lively and engaging.
AI Snips
Chapters
Transcript
Episode notes
CQRS Simplified
- CQRS is often perceived as complex, but it's fundamentally about separating reads and writes.
- This separation extends the Command Query Separation (CQS) principle from the method level to the class level.
Focus on User Intent
- Structure applications around user intent and actions, not just CRUD operations.
- This leads to a more vertical, feature-based architecture instead of application-wide layers.
.NET Migration Story
- Derek Comartin's team used CQRS and Mediator to migrate from pre-.NET Core to .NET Core.
- This approach facilitated a smoother transition and allowed them to switch from Web API to Nancy.