Attendance Gateway Interaction

Summary

Gateway routing supports independent, reversible cutover of attendance-record and Time Office compatibility surfaces.

Audience

Backend and frontend developers, architects, DevOps and support engineers, and QA engineers.

Routing model

The gateway can keep compatible attendance traffic on the monolith or route it to Attendance Service. Shift, weekly-off, and attendance-policy ownership has a separate cutover decision, allowing Time Office extraction to progress independently. Direct/shadow service paths support validation without claiming the main compatibility route. Authentication, tenant, and correlation context are forwarded downstream.

Compatibility endpoints adapt existing behavior while direct endpoints expose service-owned capability boundaries. Backfill, parity comparison, smoke testing, and go/no-go scripts support the cutover. Exact toggle names, route tables, internal destinations, and operational commands are intentionally excluded. Routing source headers/logging support diagnosis conceptually.

Source References

• microservices/src/gateway-api/Program.cs
• microservices/src/attendance-service/Api/AttendanceCompatibilityEndpoints.cs
• microservices/src/attendance-service/Api/AttendanceDirectEndpoints.cs
• microservices/src/attendance-service/Api/AttendanceShiftPolicyEndpoints.cs
• microservices/src/attendance-service/Api/ShiftPolicyCompatEndpoints.cs
• microservices/src/../docs/attendance-shift-cutover-runbook.md

Related Articles

• Technical overview
• Known limitations

See Also

• Attendance business overview

Keywords

• Attendance Service
• Attendance Gateway Interaction

Revision Information

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