Skip to main content

Recruitment Outbox and Delivery

Summary​

The outbox makes local state and publication intent atomic, while publication and downstream completion remain eventual and unproven.

Audience​

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

Overview​

Outbox records store event identity/type, serialized contract, occurrence and processing time, status, retry count, error state, correlation, shared tenant envelope, and producer identity. The shared base also contains causation, user, and schema version in the serialized payload.

Eligible pending or failed records are read in occurrence order with a bounded batch. Successful publication marks a record processed. Failure marks it failed, increments retry count, stores error evidence, and leaves it eligible for later polling.

The raw outbox publication metadata includes event identity/type, correlation, tenant, producer, and occurrence. Causation, user, and schema version remain in the serialized contract but are not added by the stored-message metadata builder.

There is no confirmed terminal retry limit, backoff schedule, dead-letter path, replay API, poison-message policy, or per-event monitoring. Exactly-once delivery, global ordering, and consumer completion must not be claimed.

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

See Also​

Keywords​

  • Recruitment events
  • Outbox and Delivery

Revision Information​

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