🔒 Paid
Dead-Letter Queue Explosion
A schema/content change is causing a large share of incoming events to fail parsing and land in the dead-letter queue, and a reprocessor has begun replaying DLQ contents back into the consumer at the same time. Events in the DLQ represent real customer activity (orders, updates, notifications) that must eventually be processed exactly once — side effects must never be applied twice, and any event that is dropped is gone for good. Diagnose why events are failing, stop the bleeding, and bring the backlog back to a safe, durable state.
- Difficulty
- Senior
- Expected Time
- ~18 min
- Category
- Messaging & Streaming
Skills
- Diagnosing schema/content-driven consumer failures
- Distinguishing a real fix from an operationally-clean-looking data-loss shortcut
- Balancing replay throughput against duplicate-processing risk
- Recognizing when scaling capacity cannot compensate for a broken parser
System Architecture
- Events
- Consumer
- Main Processing
- Dead-Letter Queue
- Reprocessor
This is a Pro scenario. Upgrade to Pro to unlock it.
Upgrade to ProBack to Incidents