Notification Consumer
Summary
Notification Service consumes EmployeeCreated from the onboarding/offboarding contract set. It does not subscribe to Recruitment onboarding/offer events or other Employee lifecycle contracts.
Audience
Notification developers, integration engineers, QA, support, privacy, and architecture reviewers.
Reference Content
Confirmed behavior
- EmployeeCreated is explicitly subscribed and mapped to a notification intent.
- Recipient resolution uses structural Employee contract information.
- Channel selection has configured overrides and defaults.
- A unique processed-event identity supports duplicate suppression.
- Infrastructure exceptions cause negative acknowledgement with requeue.
- Stale-event handling and audit evidence exist in the dispatcher.
Missing lifecycle notifications
OfferAccepted, OfferRejected, CandidateOnboarded, CandidateJoined, EmployeeUpdated, EmploymentStatusChanged and offboarding/exit events are absent from the resolver subscription set.
Compatibility Exit.Approved notification is produced through the compatibility notification service after a local exit save. It is not a shared messaging contract.
Notification contents, recipient identifiers, templates and infrastructure names are intentionally excluded.
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/notification-service/Messaging/NotificationEventConsumer.csmicroservices/src/notification-service/Application/EventNotificationResolver.csmicroservices/src/notification-service/Application/NotificationDispatcher.csmicroservices/src/notification-service/Infrastructure/NotificationDbContext.cs
Related Articles
See Also
Keywords
- Onboarding events
- Offboarding events
- Integration contracts
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly