Dead Letter Queue

Bad records kill pipelines; DLQs let you isolate failures without stopping the world

Bad records kill pipelines; DLQs let you isolate failures without stopping the world

Category

Pipeline Architecture

Difficulty

advanced

Duration

25 minutes

Challenges

0 hands-on challenges

Topics covered: "How Does Your Pipeline Handle Bad Data?", DLQ Architecture: Divert, Store, Alert, Retry Strategies and Poison Pills, DLQ Monitoring and Reprocessing, DLQ as a Data Quality Signal

Lesson Sections

1. "How Does Your Pipeline Handle Bad Data?"

   What They're Really Testing The Unlock A DLQ is not an error log. It is a parallel processing path. Good records flow through the main pipeline. Bad records are diverted to the DLQ with the full error context (original record, error message, stack trace, timestamp, retry count). The DLQ is a queue, not a graveyard. Records in it are expected to be replayed after the root cause is fixed. The 60-Second Framework This five-step flow takes 60 seconds to articulate and hits every rubric item: error c

2. DLQ Architecture: Divert, Store, Alert

   A DLQ is a separate storage destination (Kafka topic, SQS queue, S3 bucket) that captures failed records alongside their error metadata. The design has three components: diversion logic, storage schema, and alerting. DLQ Record Schema Storage Options

3. Retry Strategies and Poison Pills

   Not all errors are the same. Transient errors (network timeout, temporary database lock) should be retried. Permanent errors (malformed schema, null in a NOT NULL field) will never succeed no matter how many times you retry. The interview tests whether you can classify errors and route them differently. Retry Queue vs Dead Letter Queue Poison Pill Detection A poison pill is a message that causes the consumer to crash every time it tries to process it. Without detection, the consumer enters a cra

4. DLQ Monitoring and Reprocessing

   A DLQ without monitoring is a data graveyard. Records enter and nobody notices. The DLQ becomes a slowly growing pile of lost data that surfaces months later when a VP asks 'why are our numbers 3% lower than the source system?' The monitoring and reprocessing workflow is what makes a DLQ operational, not just architectural. DLQ Monitoring Dashboard Reprocessing Workflow Step 5 is the L6 signal. Connecting DLQ analysis back to upstream contracts shows you think about the system holistically, not

5. DLQ as a Data Quality Signal

   The senior insight that most candidates miss: the DLQ is not just an error handler. It is a data quality feedback loop. DLQ error categories and volume trends tell you which upstream producers are degrading, which schema contracts are being violated, and where your pipeline's assumptions no longer hold. The Bridge Move Vocabulary That Signals Seniority Red Flag Phrases