Leave Gateway Interaction

Summary

Gateway controls whether compatibility traffic reaches the monolith or Leave Service and also composes employee self-service Leave calls.

Audience

Frontend/backend developers, architects, QA, DevOps, and support.

Overview

The gateway recognizes Leave requests, calendar compatibility, HR workspace/balance behavior, direct Leave surfaces, and ESS composition. It forwards downstream authentication/tenant context and identifies route ownership for cutover validation.

Exact route tables, toggle names, service addresses, and operational commands are intentionally omitted. Weekly-off ownership can be claimed by Attendance before Leave routing, confirming Transitional calendar ownership. Smoke tooling covers direct, compatibility, shadow/toggle, and rollback categories.

Source References

• microservices/src/gateway-api/Program.cs
• microservices/src/gateway-api/EssEndpoints.cs
• microservices/src/leave-service/Api/LeaveEndpoints.cs
• microservices/scripts/smoke-leave.ps1

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Leave Gateway Interaction
• Technical architecture

Revision Information

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