pipeline-behaviors

MediatR pipeline behaviors apply cross-cutting concerns like logging, validation, and exception handling using the decorator pattern. This wraps your handlers externally, keeping business logic clean and free of boilerplate code.

The best way to handle validation and logging in a .NET 8 clean architecture application is using modular MediatR pipeline behaviors. They intercept requests to validate parameters via FluentValidation and log details before reaching the handler.

Yes, you can wrap database operations in a transaction using a dedicated MediatR pipeline behavior. It manages the transaction scope around your handler execution, ensuring atomic data commits without cluttering individual handler logic.

Register pipeline behaviors for exception handling and performance monitoring in your application's dependency injection setup. Add behaviors like ExceptionHandlingBehavior and LoggingBehavior to the DI container to intercept MediatR requests.

Yes, this pipeline behavior approach integrates directly with FluentValidation. A specific ValidationBehavior intercepts incoming requests, executes FluentValidation rules, and short-circuits execution by returning a failure result if parameters are invalid.

Besides validation, MediatR pipeline behaviors can manage logging, exception handling, transaction management, caching, and performance monitoring. Each concern operates as a distinct module following the chain of responsibility pattern.