It depends on your needs, but in general yes I think the DLQ (on the SQS queue, not lambda) would still be useful, because the failed messages might be permanent failures (i.e. never succeed on retry), so eventually the max number of receives would get hit, and you probably want a DLQ to capture those.
Thank you sir for your efforts for the aws development. Really appreciate 🙏🙏
My pleasure! Please like, share & subscribe. :)
Thank you very much. Excellent demo and blog.
You are welcome, Santosh! And I am glad it was helpful. Please like, share & subscribe :)
So helpful 🥰, can we have our customized class return type which is having SQSResponse inside of it, Chirag?
Nice work
Thank you! Please like, share & subscribe :)
when you set batch size to 10,why was only two messages processed?
10 is the maximum batch size. If you have 2 messages in the queue, you won't wait until you have 10 messages to process the first two that arrived.
Which tool is used to create this animation
In this video, I have used Keynote. In a few other videos, I have used Manim.
I hope this helps. Please like, share & subscribe :)
Does this work with fifo queue? I was trying but I wasn't able to see the failed messaged being reprocessed.
Would there still be a need for a DLQ if using this feature?
It depends on your needs, but in general yes I think the DLQ (on the SQS queue, not lambda) would still be useful, because the failed messages might be permanent failures (i.e. never succeed on retry), so eventually the max number of receives would get hit, and you probably want a DLQ to capture those.