Dead Letter Queues
Last Updated: February 3, 2026
In the previous chapter, we learned about delivery semantics and how at-least-once delivery retries failed messages. But what happens when a message keeps failing?
If a message has a bug, missing data, or references a resource that does not exist, no amount of retrying will help. Without a solution, these "poison" messages would either block the queue forever or consume resources with infinite retries.
Dead letter queues (DLQs) solve this problem.
A dead letter queue is a special queue that stores messages that cannot be successfully processed. Instead of retrying forever or losing the message, the system moves it to the DLQ after a configured number of attempts.
In this chapter, you will learn:
- What dead letter queues are and why they matter
- How to configure DLQs in different messaging systems
- Common reasons messages end up in DLQs
- How to handle and recover messages from DLQs
- Best practices for DLQ design and monitoring
What is a Dead Letter Queue?
A dead letter queue is a queue that stores messages that could not be processed successfully. It acts as a holding area for problematic messages that need investigation.
The Flow
- Message arrives in main queue
- Consumer attempts to process
- If processing fails, message returns to queue for retry
- After max retries, message moves to dead letter queue
- Main queue continues processing other messages