Recruitment Event Publishing Flow

Summary

Domain events become outbox records inside SaveChanges; a hosted relay later publishes eligible records.

Audience

Developers, QA and support engineers, integration reviewers, implementation partners, solution architects, and security reviewers.

Overview

Workflow start can occur after an initial requisition save and be followed by another save. Document storage can precede offer/candidate persistence. Employee provisioning precedes onboarding completion and event creation. Offer commands may raise multiple events in one save. None of these external calls participates in a distributed transaction.

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/Infrastructure/RecruitmentDbContext.cs
• microservices/src/recruitment-service/Infrastructure/Persistence.cs
• microservices/src/shared-kernel/Outbox/IntegrationEventJsonSerializer.cs
• microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
• microservices/src/recruitment-service/Messaging/OutboxRelayHostedService.cs

Related Articles

• Recruitment events documentation
• Recruitment technical documentation

See Also

• Recruitment API documentation
• Recruitment database documentation

Keywords

• Recruitment events
• Publishing Flow

Revision Information

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