pipeline-behaviors

Cross-cutting concerns in MediatR are handled using pipeline behaviors that wrap command and query handlers. This skill provides reusable behaviors for logging, validation, exception handling, and transactions to centralize these operations across your application execution pipeline.

Register MediatR pipeline behaviors in your DI container from outermost to innermost: Logging, Performance, Validation, ExceptionHandling, and Transaction. This sequence ensures logging captures the full execution context before validation short-circuits invalid requests.

Yes, FluentValidation integrates with MediatR through a ValidationBehavior pipeline component. It automatically intercepts requests, validates them against registered FluentValidation validators, and short-circuits the execution pipeline if validation fails.

Yes, the pipeline behaviors apply to both commands and queries in .NET projects. It supports open generic registrations for unified processing while including specific behaviors like QueryCachingBehavior tailored for non-mutating query operations.

Exception handling is standardized using an ExceptionHandlingBehavior that wraps handler execution. It catches exceptions thrown during processing and translates them into standardized Result or Result<T> objects for consistent error responses across the application.

Transaction management is implemented using a TransactionBehavior in the MediatR pipeline. It wraps command handlers to ensure transactional integrity across application layers, committing successful operations and rolling back failures automatically.