What is the main benefit of using CQS in .NET?

CQS ensures methods are either commands (actions) or queries (data retrieval), making code easier to reason about, test, and maintain by eliminating unexpected side effects.

How does this skill help with unit testing?

By separating side effects from data retrieval, it allows for more granular unit tests and clearer mocking of dependencies within the .NET ecosystem.

Does this skill support full CQRS architectural patterns?

Yes, it provides implementation patterns for Commands, Queries, Handlers, and Dispatchers to separate read and write responsibilities at the application level.

Are there any exceptions to the CQS rules provided?

The skill identifies valid exceptions such as atomic operations (e.g., Interlocked), fluent APIs that return 'this', and factory methods that return created objects.

.NET CQS & CQRS Patterns

Name: .NET CQS & CQRS Patterns
Author: DoubleslashSE

byDoubleslashSE

•

API Development

Implements Command Query Separation and Responsibility Segregation patterns to create predictable and testable .NET applications.

About

This skill provides specialized guidance for implementing Command Query Separation (CQS) and Command Query Responsibility Segregation (CQRS) within .NET environments. It helps developers maintain a clean separation between operations that change state (Commands) and those that retrieve data (Queries), leading to more maintainable, testable, and scalable codebases. The skill includes comprehensive patterns for method-level separation, architectural handlers, and the dispatcher pattern, while also identifying valid exceptions like fluent APIs and atomic operations to ensure practical application in real-world C# projects.

Key Features

Architectural CQRS implementation patterns for .NET
Dispatcher pattern implementation for decoupled application logic
1 GitHub stars
Method-level Command Query Separation (CQS) guidance
Standardized Command and Query handler interfaces
Best practices for handling CQS exceptions like fluent APIs and factories

Use Cases

Refactoring legacy .NET methods that mix data retrieval with state changes
Designing scalable backend microservices using CQRS and separate read/write models
Implementing clean, testable business logic with standardized handler patterns

About

Key Features

Architectural CQRS implementation patterns for .NET
Dispatcher pattern implementation for decoupled application logic
1 GitHub stars
Method-level Command Query Separation (CQS) guidance
Standardized Command and Query handler interfaces
Best practices for handling CQS exceptions like fluent APIs and factories

Use Cases

Refactoring legacy .NET methods that mix data retrieval with state changes
Designing scalable backend microservices using CQRS and separate read/write models
Implementing clean, testable business logic with standardized handler patterns