Orchestration · Data store
Dead Letter Queue
Data storeOrchestrationOrchestration & Toolsarc:DeadLetterQueue
A holding store for poison messages that repeatedly fail processing, isolating them from healthy traffic.
Responsibility. Isolates messages that exceed retry limits.
Also known as: DLQ, Poison message queue, ETL dead letter queue
Relationships
is written by dependency
receives data from dynamic
sends data to dynamic
Design guidance
- MUST receive messages automatically after retry limits are exceeded.
- SHOULD capture persistently failing events for manual review instead of losing them.
Classification
- Technologies
- AWS Lambda dead letter queues
- Quality attributes
- Reliability (ISO/IEC 25010 | NIST AI RMF: valid and reliable)
- Risks mitigated
- Poison messagesQueue congestion
Sources
- Ch1.3: T. Nguyen, "Multi-Agent Systems," in Mastering Agentic AI Systems: Guide for the NVIDIA NCP-AAI Exam, 1st ed. 2026, ch. 1.3. ISBN: 9798244538229.
- Ch4.1: T. Nguyen, "Introduction to AI Agent Deployment and Scaling," in Mastering Agentic AI Systems: Guide for the NVIDIA NCP-AAI Exam, 1st ed. 2026, ch. 4.1. ISBN: 9798244538229.
- Ch4.2: T. Nguyen, "Deployment and Scaling," in Mastering Agentic AI Systems: Guide for the NVIDIA NCP-AAI Exam, 1st ed. 2026, ch. 4.2. ISBN: 9798244538229.
- Ch6.3B: T. Nguyen, "ETL Worked Example - Load Phase & Pipeline Integration," in Mastering Agentic AI Systems: Guide for the NVIDIA NCP-AAI Exam, 1st ed. 2026, ch. 6.3B. ISBN: 9798244538229.