Dead Letter Queue
A queue that stores messages that couldn't be processed after multiple attempts. Prevents poison messages from blocking the main queue and lets you debug failures.
What is Dead Letter Queue?
A queue that stores messages that couldn't be processed after multiple attempts. Prevents poison messages from blocking the main queue and lets you debug failures.
Dead Letter Queue is a intermediate-level concept that sits in the Messaging & Event Systems area of system design. Engineers reach for it whenever they need to reason about real-world trade-offs in that space — not just for textbook correctness, but because real production systems at companies like Netflix, Amazon, and Google make these decisions every day.
If you want to go deeper than this definition — with diagrams, code, and a quiz to lock it in — work through the "Dead Letter Queue" lesson linked below. It walks through the why, the mechanism, the trade-offs, and how the giants actually use it in production.
Learn Dead Letter Queue in depth
Full interactive lesson with diagrams, code examples, real-world references, and a quiz.
Open the Dead Letter Queue lessonRelated lessons
Lessons that touch on Dead Letter Queue as part of a larger topic.
See also
Related glossary terms you might want to look up next.
Message Queue
A buffer that stores messages between producers and consumers. Messages are processed one by one, in order. Think of it as a to-do list for your services.
Retry
Automatically re-attempting a failed operation, usually with exponential backoff. Essential for handling transient failures in distributed systems.
Pub/Sub
A messaging pattern where publishers send messages to topics, and subscribers receive messages from topics they care about. Publishers don't know who's listening.