Consumer Landscape
Summary
Within the requested bounded contexts, Payroll, Leave and Notification are confirmed Employee-event consumers. No Recruitment-event consumer was found.
Audience
Integration engineers, service owners, QA, support, and architects.
Reference Content
| Consumer | Subscribed lifecycle contracts | Local effect | Idempotency |
|---|---|---|---|
| Payroll | EmployeeCreated, EmployeeUpdated, EmploymentStatusChanged | Employee payroll projection | Processed-event ledger + stale-time guard |
| Leave | EmployeeCreated, EmployeeUpdated, EmploymentStatusChanged | Leave employee projection | Last-event identity + stale-time guard |
| Notification | EmployeeCreated | Notification intents/delivery state | Unique processed-event ledger |
| Attendance | None | No Employee synchronization | Not applicable |
| Asset | None | No Employee/exit synchronization | Not applicable |
| Recruitment | None inbound | Processed ledger exists only as foundation | Foundation |
| Workflow | None for onboarding/offboarding | HTTP boundary | Not event-driven |
| Gateway | None | Route forwarding | Not event-driven |
| Compatibility | None lifecycle | Local persistence/notifications | Not event-driven |
Other source-confirmed Employee consumers exist elsewhere in the platform, but are outside the requested lifecycle bounded-context set. Their presence does not repair the missing Employee relay invocation.
Requires confirmation
Unless explicitly confirmed above, live delivery, consumer deployment, replay, reconciliation, retention, contract governance, monitoring and production ownership require confirmation.
Source References
microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.csmicroservices/src/leave-service/Messaging/EmployeeProfileConsumer.csmicroservices/src/notification-service/Application/EventNotificationResolver.csmicroservices/src/attendance-service/Program.csmicroservices/src/asset-service/Program.cs
Related Articles
See Also
Keywords
- Onboarding events
- Offboarding events
- Integration contracts
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly