Leave Integration Reference

Summary

Leave integrates synchronously and asynchronously with seven confirmed or transitional boundaries.

Developers, QA, support, architects, service owners, and implementation partners.

Boundary	Confirmed relationship	Detail
Employee	Consumes created, updated, and employment-status events into a local projection	Employee profile events
Attendance	Synchronous conflict checks; calendar ownership overlap	Attendance integration
Workflow	Optional start/callback decision orchestration	Workflow integration
Payroll	Consumes confirmed Leave lifecycle effects into a read model	Payroll events
Notification	Confirmed approval/rejection resolution; not every event	Notification events
Gateway	Direct and compatibility routing during ownership transition	Gateway interaction
Messaging	Transactional outbox publication and Employee-event consumption	Events

Payloads, endpoint tables, and database mappings remain in their dedicated sections.

microservices/src/leave-service/Program.cs
microservices/src/leave-service/Messaging/EmployeeProfileConsumer.cs
microservices/src/leave-service/Infrastructure/AttendanceServiceConflictClient.cs
microservices/src/leave-service/Infrastructure/WorkflowServiceClient.cs
microservices/src/gateway-api/Program.cs