AWS re:Invent 2019: [REPEAT 1] Moving to event-driven architectures (SVS308-R1)

Event-driven architectures are getting a lot of attention. We have recently invested in tools and infrastructure to make event-driven architectures easier to implement and operate. In this session, we discuss what events are, why the community is increasingly interested in event-centric applications, and what’s new in the domain and with AWS in particular. In addition, we discuss the challenges that still face us and our customers. By the end of this session, you understand the key principles and benefits of being event-driven.

[@loganpowell]

The best talk on the subject from AWS I've seen. Thank you!
Jump to TLDR: 42:34

[@himanshugta1724]

Great video, I really like how the content was explained in a very generalised way and not specific to any technology out there.

[@andreadiotallevi5780]

Excellent talk! Loved the pace, specificity and honesty!

[@yigidovic]

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 🎉

[@JenilCalcuttawala]

This is really a good 101 to the Event-Driven Architecture. Fantastic...!

[@Butcheren0]

Really good presentation! Clear and concise! Thanks!

[@CodyRedmond]

Great presentation! Clear, informative, and entertaining 😄

[@YazadIrani]

Great talk..lots of valid points 👍.. just wish you guys would upload timestamps too!

[@thegrumpydeveloper]

Was sweating during the message json vs binary worried I was going to have to learn to parse binary messages.

[@kitulinokitulino3360]

Great presentation !

[@1testrad]

Thanks...

[@emelinainocencio2674]

Loop

[@lepidoptera9337]

Events are a horrible idea for almost anything. You don't use events, except when you absolutely have to.

[@cristianpallares3847]

Why you think so?

[@lepidoptera9337]

@@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.

[@coderider3022]

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.

[@lepidoptera9337]

@@coderider3022 Convince your architect that he is wrong, get rid of him or find a new job.