Recruitment Outbox Storage

Summary

SaveChanges translates queued Recruitment domain events into outbox messages committed with aggregate changes.

Audience

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

Overview

Outbox storage has a primary key, globally unique event identity, and status/occurrence index. Payload is structured serialized content. No global tenant query filter is configured.

Aggregate state and outbox intent are atomic within the local save. Broker publication occurs later and is not part of that transaction. Retention, backlog thresholds, replay governance, and operational ownership require confirmation.

Requires confirmation

Production migration governance, rollback ownership, reconciliation, retention, privacy, performance, query optimization, concurrency, and operational ownership require confirmation.

Source References

• microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
• microservices/src/recruitment-service/Messaging/OutboxRelayHostedService.cs
• microservices/src/shared-kernel/Outbox
• microservices/src/shared-kernel/Messaging

Related Articles

• Recruitment database documentation
• Data integrity and transactions

See Also

• Recruitment technical documentation
• Recruitment API documentation

Keywords

• Recruitment database
• Outbox Storage

Revision Information

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