Skip to main content

Attendance Leave Integration

Summary​

Attendance Service has no direct Leave client or confirmed Leave-event consumer.

Audience​

Backend developers, Leave/Attendance integrators, architects, QA engineers, and support engineers.

Confirmed boundary​

Attendance manual commands resolve weekly offs internally but explicitly leave holiday and approved-Leave validation outside the service. Attendance monthly summaries are attendance-derived and do not compose Leave or holiday results. Current cross-domain conflict behavior is coordinated by the legacy application and user experience, not by AttendanceCalculator.

No Leave client registration, Leave repository reference, or inbound event synchronization is present in the Attendance composition root. The gateway may route weekly-off ownership to Attendance or Leave/monolith depending on cutover state, making this boundary Transitional.

Automatic Leave synchronization, event-driven conflict projection, precedence among Leave, holiday, weekly off, and worked attendance, and reconciliation after conflicting changes are Not implemented or Requires confirmation. Attendance owns actual attendance outcomes; Leave owns leave requests and approvals.

Source References​

  • microservices/src/attendance-service/Application/Services/AttendanceCommands.cs
  • microservices/src/attendance-service/Application/Services/AttendanceQueries.cs
  • microservices/src/attendance-service/Program.cs
  • microservices/src/leave-service/Program.cs

See Also​

Keywords​

  • Attendance Service
  • Attendance Leave Integration

Revision Information​

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