query-handler

Implement MediatR query handlers by delegating filtering, pagination, and sorting to repository methods via IUnitOfWork, then map results to output DTOs. This approach standardizes list and single-entity queries across your .NET microservice codebase to ensure predictable paging responses.

A paginated DTO output needs PageSize, CurrentPage, Total, and typed collections. Defining list query records with these properties ensures predictable paging responses and consistent data returns across domain repositories in your .NET application.

Handle single-entity queries by using FindAsync on named repositories through IUnitOfWork, then map the result to a DTO. If the entity is missing, throw domain-specific not-found exceptions to maintain consistent error handling across the query layer.

Yes, you can inject additional services into a MediatR query handler for enrichment when needed. The handler delegates core filtering and pagination to repository methods but supports injecting extra services to append supplementary data to the DTO output.

Yes, this approach requires repository-level encapsulation of filtering, pagination, and sorting. Handlers delegate these operations to named repositories accessed via IUnitOfWork, preventing duplicated query logic and incorrect data returns across the microservice codebase.

Standardize query logic by using MediatR query handlers that delegate to IUnitOfWork named repositories for filtering and pagination. This reduces duplicated logic by enforcing repository-level encapsulation and returning DTOs with consistent PageSize, CurrentPage, and Total properties.