Technical detail ยท Message Queue Challenges
Delivery promises and the crash before acknowledgment
At-most-once delivery does not retry a delivery, avoiding transport duplicates at the cost of possible loss after a crash. Important lost work needs an independent recovery path. At-least-once delivery retries unacknowledged work, so duplicates can follow retries or reconnects. A worker should acknowledge only after its protected work completes.
An effective exactly-once result means each message takes effect once. It requires protection beyond transport: durable identity with deduplication, an idempotent operation, or both. At-least-once delivery with that protection can provide the effective result, but partial state remains a risk if the protection is implemented carelessly. The cost and complexity belong in the design review.
The revealing crash occurs after a side effect but before acknowledgment. The queue can redeliver on restart. A stable identifier must let the target retain one result while the worker acknowledges the repeated delivery. This separates transport completion from application completion; a delivery promise alone cannot establish what changed at the target.