AWS Serverless Hero, Independent Consultant. Follow me to learn practical tips and best practices for AWS and Serverless.
Another massive announcement just before re:Invent. Payload-based filtering was one of the key reasons why you'd choose EventBridge over SNS. This new feature makes SNS a much more viable option in an Event-Driven Architecture. Off the top of my head, this would: 1. allow you to use one SNS topic for many types of messages, previously one tends to have many SNS topics 2. reduce the coupling between publisher and consumer teams (i.e. no need to pester the publisher team to add a message attribute so you can filter) 3. just make message filtering easier when you're not limited to what's in the message attributes (and you can only have 10!) To be clear, there are still many reasons to choose EventBridge over SNS - event archive, replay, cross-account delivery, many more targets, etc. But for really simple use cases, SNS is now a more viable option. And not to mention, it has FIFO support, which EventBridge doesn't. So in some cases, it might be a BETTER option than EventBridge. #aws #serverless https://lnkd.in/eszZFngd
Gregor Hohpe
1y
I'll have to update some of my slides for re:Invent :-)
Tomasz Dudek
1y
Lines between EventBridge and SNS are getting blurrier.
Lukas Liesis
1y
yesss, ty for sharing 🤌👏
Reza Alirezaei
10mo
Honestly with this new feature in, customers are even more confused whether to use SNS or EventBridge!
Great stuff, thanks for the detailed explanation and comparison with EventBridge
Mark O.
1y
Extremely useful feature!
Mohd Arshad
1y
Extremely useful!
Wow, nice
Making Sense of Dynamics 365 & Integrated Systems in Azure and AWS
1yClemens Vasters Eldert Grootenboer this would be a great value add to your product