Skip to main content

Performance Outbox Operations

Summary​

The outbox is written in the local Performance transaction. The hosted relay repeatedly selects bounded Pending/Failed work and records publication results.

Safe diagnostics use supported outbox reads and sanitized status counts/time windows. Persisted intent is not delivery proof. No terminal retry limit, dead-letter policy, replay tool, or reconciliation owner is confirmed; direct status/data modification is outside this guide.

Safety and confirmation boundary​

No production command, secret, configuration value, internal address, infrastructure detail, direct data change, or replay instruction is provided. Production ownership, approvals, service objectives, alerting, and recovery authority require confirmation.

Source References​

  • microservices/src/performance-service/Infrastructure/PerformanceDbContext.cs
  • microservices/src/performance-service/Messaging/OutboxRelayHostedService.cs
  • microservices/src/shared-kernel/Messaging/OutboxProcessor.cs

See Also​

Keywords​

  • Performance operations
  • Safe support guidance

Revision Information​

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