Skip to main content

Attendance Event Consumer Landscape

Summary

Only Payroll Service and Integration Service have confirmed Attendance subscriptions in current source.

Audience

  • Service owners, integration engineers, architects, QA engineers, and support engineers

Reference Content

ServiceClassificationConfirmed Attendance scope
Payroll ServiceRead-model consumerSubmitted and Approved
Integration ServiceDirect consumer / routerSubmitted, Approved, Rejected
Notification ServiceNo confirmed consumerResolver subscription list has no Attendance contract
Platform ServiceNo confirmed consumerCurrent audit consumer binds other event types
Leave ServiceNo confirmed consumerConsumes employee-profile events only
Document ServiceNo confirmed consumerCurrent read-model list excludes Attendance
Employee ServiceNo confirmed consumerProduces Employee events; no Attendance subscriber
Reporting ServiceSkeleton/no implementationService shell has no event consumer
Attendance ServiceProducerFive lifecycle contracts; no self-consumer

Configured Integration Service downstream routes may reference Payroll or notification targets, but such routing is Transitional and can be log-only. It is not evidence that those target services directly consume the shared contract.

Source References

  • microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
  • microservices/src/integration-service/Domain/IntegrationEntities.cs
  • microservices/src/notification-service/Application/EventNotificationResolver.cs
  • microservices/src/platform-service/Messaging/PlatformEventConsumer.cs
  • microservices/src/leave-service/Messaging/EmployeeProfileConsumer.cs
  • microservices/src/document-service/Messaging/DocumentReadModelConsumer.cs
  • microservices/src/reporting-service/Program.cs

See Also

Keywords

  • Attendance events
  • Integration contracts
  • Eventual consistency

Revision Information

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