Skip to main content

Attendance Command and Query Flow

Summary​

Minimal API delegates call scoped application services directly. MediatR is absent.

Audience​

Backend developers, frontend integrators, architects, and QA engineers.

Command flow​

Query flow​

Expected failures use Result<T>; query methods generally return collections directly. Presentation maps these results to responses. There is no central pipeline behavior for validation, authorization, logging, or transactions; each boundary is composed explicitly.

Source References​

  • microservices/src/attendance-service/Api/Endpoints.cs
  • microservices/src/attendance-service/Application/Common/Cqrs.cs
  • microservices/src/attendance-service/Application/Services/AttendanceCommands.cs
  • microservices/src/attendance-service/Application/Services/AttendanceQueries.cs
  • microservices/src/attendance-service/Infrastructure/Persistence.cs

See Also​

Keywords​

  • Attendance Service
  • Attendance Command and Query Flow

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-15
  • Review cycle: Quarterly