controller-patterns

To keep ASP.NET Core controllers thin and testable, route API requests through MediatR commands and queries. This delegates complex business workflows to separate handlers, ensuring a maintainable architecture with separated concerns.

The best way to structure REST operations in an ASP.NET Core Web API is to use resource-based URLs with explicit response types via ProducesResponseType. This enforces standard routing and consistent error handling using ProblemDetails.

MediatR works with ASP.NET Core controllers by dispatching API requests directly to MediatR commands and queries. Controllers simply coordinate the request, while MediatR handlers process the complex business logic asynchronously.

Yes, you can use cancellation tokens with MediatR handlers in ASP.NET Core. The controller pattern supports robust model binding and passes cancellation tokens to handlers to gracefully terminate long-running API operations.

To configure an ASP.NET Core app for MediatR, enable the ApiController feature, register MediatR in the dependency injection container, and implement specific request handlers to process commands and queries.

ASP.NET Core API controllers contain too much business logic when they directly coordinate complex workflows. Delegating this logic to MediatR commands and queries separates concerns, keeping controllers focused strictly on routing and HTTP response mapping.