Recruitment Event Overview
Summary
Aggregate domain events are in-process state-change evidence; mapped shared contracts become durable outbox publication intent.
Audience
Developers, QA and support engineers, integration reviewers, implementation partners, solution architects, and security reviewers.
Overview
Domain events implement the Recruitment-local IDomainEvent contract. Shared integration contracts derive from IntegrationEvent and add envelope metadata plus event-specific information. Mapping occurs in the DbContext before the local save.
Recruitment produces from Candidate, Interview, Offer, and Onboarding aggregates. Requisition and Job Opening do not raise domain events. Audit/timeline records are staged by commands rather than event handlers.
The mapping creates a new integration-event identity. It sets schema version one, sets correlation to the candidate identifier, leaves causation/user/shared tenant envelope unset, and retains occurrence time. Persisted intent proves neither broker delivery nor consumer completion.
Requires confirmation
Consumer ownership, tenant-envelope policy, correlation/causation policy, retry limits, replay, ordering, contract governance, reconciliation, monitoring, and production support require confirmation.
Source References
microservices/src/recruitment-service/Domain/Common/DomainPrimitives.csmicroservices/src/recruitment-service/Domain/Recruitment/RecruitmentDomainEvents.csmicroservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.csmicroservices/src/contracts/Events/IntegrationEvent.csmicroservices/src/recruitment-service/Messaging/OutboxRelayHostedService.cs
Related Articles
See Also
Keywords
- Recruitment events
- Event Overview
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly