Skip to main content

Leave Operational Overview

Summary​

Leave Service starts an HTTP API, persistence, telemetry, an outbox relay, and an Employee projection consumer, with external Attendance and optional Workflow dependencies.

Audience​

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

Overview​

Startup registers tenant context, authentication/authorization, persistence, application workflows, external clients, observability, health, and hosted services. Migration behavior is controlled by startup configuration and must be validated through approved deployment evidence.

Runtime dependencies are the Leave data store, identity/tenant context, messaging for relay and projection, Attendance conflict checking, optional Workflow orchestration, and gateway routing. Payroll and Notification are downstream asynchronous consumers rather than synchronous startup dependencies.

Support ownership crosses Leave, gateway, Employee integration, Attendance, Workflow, data, messaging, and platform operations. Key risks are coexistence divergence, process-only health, missing dependency metrics/probes, background retry visibility, incomplete employee deletion propagation, and optional Workflow state reconciliation.

Source References​

  • microservices/src/leave-service/Program.cs
  • microservices/src/leave-service/Infrastructure/Persistence.cs
  • microservices/src/leave-service/Messaging/OutboxRelayHostedService.cs
  • microservices/src/leave-service/Messaging/EmployeeProfileConsumer.cs

See Also​

Keywords​

  • Leave operations
  • Leave Operational Overview
  • Service support

Revision Information​

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