Purpose and setup of a Dead-Letter Queue
WHAT IT TESTS: handling unprocessable messages. OUTLINE: a DLQ captures messages that repeatedly fail so they neither block the queue nor get lost; configure a redrive policy with a max receive count and alarm on it. RED FLAG: silently dropping failures.
WHAT IT TESTS: whether you isolate poison messages without losing data or blocking the queue. ANSWER OUTLINE: a DLQ is a separate queue that captures messages a consumer cannot process after a set number of attempts, preventing poison messages from blocking the main queue or being dropped. Configure it with a redrive policy that names the DLQ and sets maxReceiveCount; after that many failed receives the message moves to the DLQ, where you alarm, inspect, fix, and redrive. RED FLAG: discarding failures silently or having no retry cap.
Read the original → interview
- #serverless
- #messaging
- #sqs
- #reliability
- #dlq
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.