You did a great job while explaining complex details in a simple way - thanks for sharing them! As a PM comes from non-CS background, I get the basics of event driven architecture thanks to this video 🎉
@@cristianpallares3847 Overhead, if nothing else. Scheduling conflicts. It's like interrupts but without the priority hardware. And yes, interrupts are a horrible idea, unless you absolutely have to.
Yes, I have an architect which thinks we need a full blown event driven architecture to submit a json message then perform a 2nd action if it succeeds. I think we should look more at durable / step functions on small scale.
![AWS re:Invent 2019: [REPEAT 2] I didn’t know Amazon API Gateway did that (SVS212-R2)](http://i.ytimg.com/vi/yfJZc3sJZ8E/mqdefault.jpg)
![AWS re:Invent 2019: [REPEAT 2] I didn’t know Amazon API Gateway did that (SVS212-R2)](/img/tr.png)
![AWS re:Invent 2019: [REPEAT 3] Serverless architectural patterns and best practices (ARC307-R3)](http://i.ytimg.com/vi/9IYpGTS7Jy0/mqdefault.jpg)
![AWS re:Invent 2019: [REPEAT] Best practices for CI/CD using AWS Fargate and Amazon ECS (CON333-R)](http://i.ytimg.com/vi/7FVK0i9edyg/mqdefault.jpg)
The best talk on the subject from AWS I've seen. Thank you!
Jump to TLDR: 42:34
Excellent talk! Loved the pace, specificity and honesty!
Great video, I really like how the content was explained in a very generalised way and not specific to any technology out there.
You did a great job while explaining complex details in a simple way - thanks for sharing them! As a PM comes from non-CS background, I get the basics of event driven architecture thanks to this video 🎉
This is really a good 101 to the Event-Driven Architecture. Fantastic...!
Great talk..lots of valid points 👍.. just wish you guys would upload timestamps too!
Great presentation! Clear, informative, and entertaining 😄
Great presentation !
Really good presentation! Clear and concise! Thanks!
Was sweating during the message json vs binary worried I was going to have to learn to parse binary messages.
Thanks...
Loop
Events are a horrible idea for almost anything. You don't use events, except when you absolutely have to.
Why you think so?
@@cristianpallares3847 Overhead, if nothing else. Scheduling conflicts. It's like interrupts but without the priority hardware. And yes, interrupts are a horrible idea, unless you absolutely have to.
Yes, I have an architect which thinks we need a full blown event driven architecture to submit a json message then perform a 2nd action if it succeeds. I think we should look more at durable / step functions on small scale.
@@coderider3022 Convince your architect that he is wrong, get rid of him or find a new job.