Leave Technical Overview

Summary

This section documents the Leave Service architecture, domain, application, infrastructure, integrations, runtime boundaries, and technical maturity without duplicating detailed API, database, event, or operational documentation.

Audience

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

Overview

Leave Service is a .NET 8 ASP.NET Core service for the Leave bounded context. Minimal API presentation invokes scoped application services directly. Domain aggregates own state transitions and calculations. EF Core/PostgreSQL persistence, tenant filtering, audit/timeline data, external clients, employee-profile consumption, and transactional outbox publication sit behind infrastructure and messaging boundaries.

Runtime dependencies include identity-bearing tenant context, persistence, shared messaging, Employee events, Attendance conflict checks, optional Workflow delegation, gateway routing, and downstream Payroll/Notification consumers. Monolith compatibility and gateway cutover remain Transitional.

Documentation map

• Architecture, responsibilities, project structure, and layers
• Domain model, request aggregate, balance/policy, calendar, and carry-forward/encashment foundation
• Calculator, application, infrastructure, repositories/unit of work, command/query flow, and validation
• Tenant, employee profile, Attendance, Workflow, Payroll, Notification, and Gateway
• Messaging/outbox, dependency injection, configuration, security, observability, health, performance, testing, limitations, and future evolution

Future detailed categories remain in API, Database, Events, UI, Operations, Reference, and Troubleshooting.

Source References

• microservices/src/leave-service/Program.cs
• microservices/src/leave-service/leave-service.csproj
• microservices/src/leave-service/Application/LeaveWorkflows.cs

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Leave Technical Overview
• Technical architecture

Revision Information

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