request-response

Design CQRS request/response contracts by creating typed request and response DTOs, wrapping outcomes in a Result<T> type, and enforcing immutability to provide clear success and failure semantics for your domain logic.

Integrate FluentValidation by creating validators for your commands and queries, applying rules to nested DTOs, and leveraging automatic validator registration to enforce immutability and validation before the handler executes.

The Result<T> pattern wraps the return value of CQRS handlers to explicitly represent success and failure outcomes, ensuring immutability and clear separation between request handling and domain logic without throwing exceptions.

Yes, this approach supports async validation and nested DTOs by applying FluentValidation rules hierarchically within the request/response contracts, ensuring complex business workflows maintain immutability and robust validation.

Use immutable request and response DTOs in CQRS to prevent side effects during command and query processing, ensuring that validation rules and handler logic operate on unchanging data throughout the request lifecycle.