net-cqrs

Implementing CQRS with MediatR in .NET involves separating command and query handlers, configuring pipeline behaviors, and using FluentValidation. This approach provides a ready-to-use template for maintainable, scalable code across enterprise-grade services.

The best way to handle validation in a .NET CQRS pipeline is using FluentValidation within MediatR pipeline behaviors. This ensures commands are validated before execution, maintaining clean architecture boundaries and preventing invalid state mutations.

Domain event publishing with MediatR commands works by dispatching events through the MediatR pipeline after a command handler processes a mutation. This allows decoupled notification of state changes across your Clean Architecture setup.

Yes, you can use this CQRS template for both reads and writes in a .NET application by implementing dedicated query handlers for reads and command handlers for mutations. This separation ensures optimized, maintainable data access.

You should separate commands and queries in a .NET application when building complex, enterprise-grade services that require scalable and maintainable code. Using CQRS with MediatR allows independent evolution of read and write logic.

MediatR supports transactional behavior and event sourcing basics in .NET through pipeline behaviors and domain event publishing. This allows you to coordinate mutations and dispatch events reliably within a Clean Architecture setup.