After building serverless applications for quite a few years, we decided to share some important pieces and concepts for production-ready serverless projects. This time: Why you should utilize Dead Letter Queues when building event-driven systems. More Information: https://lnkd.in/dnY6cNnG

1. Dead Letter Queues
?
Serverless on AWS
lessons learned #2
Are you really
production-ready?

2. What happens when
your Lambda fails to
process a message?

3. The message remains
in the queue and will be
re-processed after
some time*
*visibility timeout

4. Where is the
problem?

5. If the error remains,
this message will be
processed over and
over again.
Which can lead to high
load and cost.

6. Dead Letter Queue
(DLQ)

7. Setup a Dead Letter
Queue and define a
max retry count.
Messages that couldn’t
be processed will be
stored there for later
analysis.

9. Dead Letter Queues

10. thumbs up, comment, share
What are your thoughts?
Is anything important missing?
If you liked it, please leave a comment.
connect with me!