Shared flowchart

Software · L3 · Message Delivery and Failure Handling

From publish through at-least-once delivery, idempotent processing, and dead-letter routing after repeated failure.

by @openstemUpdated Software
Business transaction commitsOutbox row written in same transactionRelay process publishes to queueConsumer receives messageIdempotency key already processed?Skip: safe no-opApply side effectProcessing succeeded?Record idempotency key, ack messageRetry count under limit?Redeliver after backoffRoute to dead-letter queueOperator inspects and replays after fixYesNoYesNoYesNo

We use privacy-friendly product analytics (no session recording, PII masked) to improve OpenStem. Load analytics? Privacy Policy