Leave Service Project Structure

Summary

The service is a single .NET web project with explicit source folders and external validation tooling.

Audience

Developers, QA, architects, and new engineers.

Overview

Path	Responsibility
microservices/src/leave-service/Api/	Minimal API presentation and capability grouping.
.../Application/	Orchestration services, queries, DTOs, result model, ports, and Workflow options.
.../Domain/	Aggregates, entities, invariants, calculator, domain events, and repository ports.
.../Infrastructure/	EF Core persistence, tenant context, repositories, external HTTP adapters, migrations, and development seeding.
.../Messaging/	Outbox relay and Employee profile consumer.
.../Properties/	Local launch metadata.
.../Program.cs	Composition root and middleware pipeline.
.../appsettings*.json	Runtime configuration sources; values are intentionally not documented.
microservices/scripts/smoke-leave.ps1	Leave, compatibility, Employee-sync, Attendance-conflict, and optional Workflow smoke coverage.

No service-specific source documentation folder or formal Leave test project was found.

Source References

• microservices/src/leave-service/Program.cs
• microservices/src/leave-service/leave-service.csproj
• microservices/scripts/smoke-leave.ps1

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Leave Service Project Structure
• Technical architecture

Revision Information

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