Dead letter queue
A dead-letter queue is a destination for messages or records that cannot be delivered or processed through the normal path, typically for later inspection or handling.
MongoDB 8.0 in Action, Third Edition
A dead-letter queue is a queue that stores messages or records that cannot be processed so they can be inspected, reprocessed, or discarded later.
- How it is used
- Keeps stream processing moving by separating unprocessable records for later inspection and handling.
- How deep it goes
- Explains processor-level configuration, validation routing, and operational practices; notes that validationAction "dlq" logs without guarantees.
- Examples
- Illustrates failed dailySales validation and a Kafka-backed processor configured to store problematic records in ErrorLogs.TransactionErrors.
- What you can do after
- Operate/configure it with sp.createStreamProcessor, then monitor the MongoDB collection and plan how to handle failed records.
Read how MongoDB 8.0 in Action, Third Edition explains dead letter queue →
Grokking Software Architecture
A dead letter queue is a specialized holding queue for messages that remain unprocessable after a defined number of delivery attempts.
- How it is used
- Holds messages that exceed configured delivery attempts so they do not block the main queue.
- How deep it goes
- Defines retry-limit routing and monitoring, while placing retry configuration in infrastructure settings.
- Examples
- Uses a crashing consumer and a retry-policy configuration with a delivery limit and exponential backoff.
- What you can do after
- Operate a DLQ by setting a finite delivery limit, monitoring failures, and requeueing messages after fixing their cause.
Read how Grokking Software Architecture explains dead letter queue →
Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
A dead-letter queue is a queue that receives messages that exceed a configured number of unsuccessful processing attempts.
- How it is used
- Supports fault-tolerant image-processing infrastructure alongside an SQS queue.
- How deep it goes
- Defines the retry-threshold destination but stops short of showing its queue configuration or processing behavior.
- Examples
- Uses the Imagery application and its CloudFormation deployment as the concrete infrastructure example.
- What you can do after
- Operate a deployed SQS-based application whose infrastructure includes a dead-letter queue.
Architecting an Apache Iceberg Lakehouse
A dead-letter queue is a side channel that stores records rejected or unprocessable by a normal data-processing path for later inspection or correction.
- How it is used
- Keeps ingestion operational while isolating rejected records for later inspection or correction.
- How deep it goes
- Explains placement within hybrid error handling but stops short of specifying queue formats, retention, or replay procedures.
- Examples
- Uses problematic rows from semistructured or external sources and unresolvable ingestion errors as representative DLQ contents.
- What you can do after
- Operate resilient ingestion by combining critical-field checks, controlled casting, automated recovery, and DLQ redirection.
Read how Architecting an Apache Iceberg Lakehouse explains dead letter queue →
Build High Value Software Systems
A queue that holds messages or work items that could not be processed successfully through the normal path.
- How it is used
- Keeps queue processing moving by isolating poison messages and preserving failures for investigation.
- How deep it goes
- Specifies validation, immediate routing for invalid data, limited retries for transient failures, and investigation of accumulating messages.
- Examples
- Uses a corrupted event with malformed data, plus database timeouts and network blips.
- What you can do after
- Operate queue handling by validating messages, retrying transient failures a limited number of times, and routing persistent failures to a DLQ.
Read how Build High Value Software Systems explains dead letter queue →
Kafka Streams in Action, Second Edition
A dead letter queue is a Kafka topic that stores records a connector cannot deliver or process successfully.
- How it is used
- Handles sink-connector failures by preserving undeliverable records while the connector continues processing.
- How deep it goes
- Configures tolerance, topic naming, headers, and replication, but does not detail DLQ consumption or replay procedures.
- Examples
- Uses an Elasticsearch sink connector writing failed records to the orientation_student_dlq topic.
- What you can do after
- Operate/configure a Kafka Connect sink connector with continued processing and diagnosable failed records.
Read how Kafka Streams in Action, Second Edition explains dead letter queue →
Also covered in
- Apache Kafka in Action
- C# Concurrency: Asynchronous and multithreaded programming
- ActiveMQ in Action
What to know first
- load balancingLoad balancing is the distribution or adjustment of work across multiple resources to manage demand and reduce overload or imbalance.
- schemaA data schema is a formal specification of the structure, fields, types, relationships, and constraints of data.
- sink nodeA sink node is a destination component or endpoint that receives data, messages, events, or flow from an upstream source for consumption or processing.
- contractA contract is an agreed specification of the conditions, expectations, rights, or obligations that govern behavior or interactions between parties or software components.
Related concepts
- ActiveMQ advisory messageproduces · An ActiveMQ advisory message is a broker-generated message that reports events or state changes within the broker.
- Atlas Stream Processingused by · Atlas Stream Processing is a MongoDB Atlas capability for processing continuously arriving data streams with MongoDB's data model and query operations.
- jidokaimplements · A Lean production approach that builds quality into processes by stopping when abnormalities occur and preventing defects from proceeding.
- topicimplemented by · A topic is a named channel or category that groups messages or records for publication and delivery to interested consumers.
- permanent failureaddressed by · A permanent failure is a failure condition that is not resolved by repeating the same operation without changing the request or relevant system conditions.
- retryaddresses · A retry is a subsequent attempt to perform an operation after an earlier attempt fails or does not complete successfully.
Questions about dead letter queue
What is dead letter queue?
A dead-letter queue is a destination for messages or records that cannot be delivered or processed through the normal path, typically for later inspection or handling.
Which Manning books explain dead letter queue?
MongoDB 8.0 in Action, Third Edition, Grokking Software Architecture, Amazon Web Services in Action, Third Edition: An in-depth guide to AWS, Architecting an Apache Iceberg Lakehouse, Build High Value Software Systems and Kafka Streams in Action, Second Edition.
What should I know before learning dead letter queue?
Manning books that teach dead letter queue usually introduce load balancing, schema, sink node and contract first.
What is dead letter queue also called?
Dead letter queue is also called DLQ.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.





