Skip to main content

Performance Retry and Failure Handling

Summary​

Failure boundaries are independent.

No terminal outbox limit, dead-letter/poison policy, replay owner, or reconciliation owner is confirmed. Workflow, compatibility, and backfill failures remain separate request/job boundaries.

Requires confirmation​

Operational ownership, service objectives, reconciliation, replay, and future consumer governance require confirmation where not explicitly implemented.

Source References​

  • microservices/src/performance-service/Messaging/OutboxRelayHostedService.cs
  • microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
  • microservices/src/notification-service/Messaging/NotificationEventConsumer.cs
  • microservices/src/notification-service/Application/NotificationDispatcher.cs

Revision Information​

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