What is a DLQ, and how do you return to failed messages?
Answer out loud or in your head first, then compare.
Answer
A DLQ, or dead-letter queue, is a separate queue for messages that couldn't be processed correctly under the agreed rules. With it, one permanently failing item doesn't circulate endlessly in normal traffic. But someone has to notice the problem and fix it.
Before resending, I check the cause of the error, whether the data is still current, and whether the effect has already been saved. I replay gradually and keep the original operation's identifier. If I give every attempt a new ID, I can bypass my own duplicate protection. Alarms, retention and someone responsible for handling it matter — not just creating the DLQ.
Why it matters: Teaches maintaining a queue after failures.
Possible follow-ups: Can you safely replay a message after the user or document has been deleted?
How did it go? Be honest — “Not yet” puts the question on your review list.
Start with
- E-P01 · What is cloud computing? — AWS, Cloudflare and infrastructure
- E-P03 · What is Cloudflare, and what is it for? — AWS, Cloudflare and infrastructure
- E-P04 · How does Cloudflare differ from AWS? — AWS, Cloudflare and infrastructure
Further reading
- AWS: Using Lambda with Amazon SQS(opens in a new tab)Docs; accessed 22.10.2026. Polling, batches, duplicates and partial batch responses.