mediator-commands-queries

MediatR use cases enforce CQRS boundaries by keeping each command and query in a single cohesive UseCases/<Feature>/<CaseName> folder, separating validators into distinct files, and mapping namespaces to features instead of technical layers like Commands or Handlers.

The best way to organize MediatR commands and queries is grouping them by use case rather than technical function. Each use case lives in a single cohesive folder under Application.UseCases, preventing cross-cutting folders and keeping related logic together.

MediatR use case logic scatters when you split Commands, Queries, and Handlers into separate cross-cutting folders. Standardizing on a single UseCases/<Feature>/<CaseName> folder structure keeps all related logic cohesive and prevents code fragmentation.

To separate validators in a MediatR CQRS project, place each validator in a separate file within the same use case folder. This keeps validation logic isolated from the handler while maintaining the cohesive folder structure under Application.UseCases.

Yes, you can migrate existing MediatR commands and queries into a standardized CQRS folder structure. Moving use cases under Application.UseCases/<Feature>/<CaseName> ensures one request per use case, proper naming, namespace structure, and shared CQRS abstractions.

MediatR handlers in a CQRS application should orchestrate flow without leaking domain logic, propagate cancellation tokens, use shared CQRS abstractions, and follow strict architecture rules ensuring commands model write intent and queries model read-only operations.