113
dead-letter queue
Jobs that failed enough times go somewhere a human can see. They do not retry forever, and they do not vanish.
What is dead-letter queue?
A dead-letter queue holds messages a consumer rejected past a retry limit. They wait for a fix and a replay. Without one, poison messages block a partition or get acked and lost.
Why does dead-letter queue matter when vibe coding?
Models catch errors, log them, and ack. The work is gone. Or they nack forever and the queue stalls. Name the retry cap and the dead letter.
How do you do dead-letter queue?
Retry with backoff and a max. Then dead-letter with the error and the payload. Replay is an explicit action after the bug is fixed. Alert on depth, not on the first failure.
How do you ask a model for dead-letter queue?
Retry (job) with backoff up to (N) times. Then move it to a dead-letter queue with the error. Do not ack a failure away. Do not retry forever. Alert when the dead-letter depth is non-zero.
What goes wrong with dead-letter queue?
A dead letter nobody owns. It is a landfill. Name who replays it.