pipeline-behaviors

Cross-cutting concerns in MediatR are handled using pipeline behaviors. This approach provides ready-to-use behaviors for logging, validation, exception handling, and caching, centralizing these tasks instead of scattering them across individual handlers.

The best way to implement caching and performance monitoring for MediatR queries is through pipeline behaviors. They automatically wrap handler execution to cache query results and detect slow operations for observability.

Yes, the MediatR pipeline behaviors are applicable to .NET 8+ applications. They integrate directly with dependency injection registration to ensure correct outer-to-inner execution order for commands and queries.

To ensure correct execution order for MediatR pipeline behaviors, they must be registered correctly in your dependency injection container. This skill implements open generic behaviors and enforces non-modification of requests to maintain proper outer-to-inner execution.

Yes, you can automatically wrap MediatR command handlers in database transactions using pipeline behaviors. This centralizes transaction management across applicable commands without modifying the core handler logic.

Request validation fails before reaching the handler when a validation pipeline behavior intercepts the execution. This behavior validates requests prior to handler execution, ensuring invalid commands and queries are stopped early in the pipeline.