I think in the decision tree you could factor in an economic component of invoking lambda directly vs batching lambda's. I saw another talk where this was advertised as more cost-effective.
Is it actually deliver-once? What if a new subscriber comes later - will it deliver-once from the beginning of all messages? I know the answer is no, and its not a bad answer that something will be delivered-once, when it starts; however, its important to recognise, that deliver-once when I've started listenning.
This presentation is just wow - great stuff!!
That's amazing to hear! 😀 👍
Fantastic detail on this presentation. Comparisons helped clarify when to use SNS vs SQS. Great presentation!
What a talk! ❤
So much useful material in this presentation and all of it explained clearly. Thank you!
Happy to hear you enjoyed it, Joel. ⛅ Best of luck as you traverse the cloud! ^JM
Fantastic insight! Thanks Justin.
Thoroughly explained ! Thanks for video
really in depth, super thanks
Great detailed end to end implementation
Thanks for in-depth explanation!
This video makes my day!
One of the best and short :) thx!
I think in the decision tree you could factor in an economic component of invoking lambda directly vs batching lambda's. I saw another talk where this was advertised as more cost-effective.
Thank you for this video, very well explained.
Thank you. Very important Info.
great overview!
Awesome content..great lecture.
Awsome
Excellent - very useful indeed
Thank you.
Well explained!
🎉🎉🎉
With what for a tool your making your prasantations
Very informative. Much appreciated!
Is it actually deliver-once? What if a new subscriber comes later - will it deliver-once from the beginning of all messages? I know the answer is no, and its not a bad answer that something will be delivered-once, when it starts; however, its important to recognise, that deliver-once when I've started listenning.
nice