Dead Letter Queues Explained: How Distributed Systems Handle Failed Messages

A dead-letter queue (DLQ) is a mechanism in message-driven systems that captures messages a consumer repeatedly fails to process, preventing queue blockages or silent data loss. Rather than discarding or stalling on a problematic payload, the broker routes it to a separate queue after a configurable retry threshold is crossed. Major platforms implement this differently: Amazon SQS uses a redrive policy, RabbitMQ relies on exchange arguments and rejection flags, Azure Service Bus triggers it automatically after exceeding a delivery count, while Apache Kafka requires developers to build the pattern manually at the consumer level. Once quarantined in a DLQ, engineers can inspect the failed message, identify the root cause, and decide whether to replay it or discard it permanently. The pattern ultimately converts an invisible system failure into a visible, actionable event that teams can monitor and resolve deliberately.