dotnet-cqrs-api

Structure .NET CQRS APIs by organizing code into feature-based vertical slices using MediatR for command and query dispatch, Carter for endpoint routing, and FluentValidation for handler-level validation. This approach standardizes Add, Get, List, and Update operations across features.

Handle errors in MediatR-based .NET APIs by enforcing a Result<T> error model throughout your handlers. This pattern standardizes validation failures and domain errors, returning consistent typed results instead of throwing exceptions across your CQRS operations.

Carter works with MediatR and FluentValidation to build minimal APIs by handling endpoint routing while MediatR manages command and query dispatch, and FluentValidation executes validation logic directly inside handlers for each vertical slice.

Implement dependency injection in vertical slice .NET APIs using constructor-based injection within your MediatR handlers. This approach keeps each feature slice self-contained while maintaining testability and platform-agnostic API design across your CQRS architecture.

Add OpenAPI metadata to Carter-based .NET API endpoints by defining documentation directly within your endpoint definitions. This ensures each vertical slice exposes its own API contracts, covering all Add, Get, List, and Update operations consistently.

Use vertical slice architecture for .NET CQRS APIs when you want to group related commands, queries, and handlers by feature rather than technical concern. This reduces cross-cutting dependencies and simplifies testing compared to traditional layered designs.