Leave Layered Architecture

Summary

Presentation delegates directly to application services; application code coordinates domain objects through ports implemented by infrastructure.

Audience

Backend developers, architects, QA, and new engineers.

Overview

Presentation performs request binding and response translation. Application services orchestrate validation, repository lookups, external checks, domain mutation, audit/timeline recording, and DTO mapping. Domain code is infrastructure-independent. Infrastructure implements ports with EF Core and HTTP clients. Messaging hosts publication and Employee projection consumption. Dependency direction is enforced by namespaces/project organization rather than separate assemblies.

Source References

• microservices/src/leave-service/Api/LeaveEndpoints.cs
• microservices/src/leave-service/Application/LeaveWorkflows.cs
• microservices/src/leave-service/Domain/Repositories.cs
• microservices/src/leave-service/Infrastructure/Persistence.cs

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Leave Layered Architecture
• Technical architecture

Revision Information

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