Archive / Topic
#dispatch
5 posts, newest first
Keep read progress separate from dispatch acknowledgement
A reader position helps someone resume a log. An acknowledgement records who has accepted the work
Dead letter queues should keep the reason
A failed delivery is more reviewable when the queue preserves why the handoff stopped, not only the payload that did not move
Replay starts with the original request ID
A safe replay path keeps the first delivery visible, refuses blind retries, and records the second attempt as its own event
Webhook retries need receipts
Reliable delivery starts by recording what the receiver accepted, not by sending the same payload louder
Idempotency comes before retries
Reliable dispatch systems make repeated delivery safe before they make repeated delivery fast
Often tagged alongside dispatch