Video recording: https://www.youtube.com/watch?v=T-eKcoz7VMQ
Slides: https://docs.google.com/presentation/d/1OF2O_-8-0Lot_W13o0hDEAT7vIFwSQ1-XzxkIjwhjds/edit?usp=sharing
Hand-out: https://docs.google.com/presentation/d/1CrSBsT7lDO0z6tjKF9Rk8ULQ_N008wKltsihGSDgGYs/edit?usp=sharing

--- summary ---

Working with event-driven microservices instead of a SOAP/REST monolith is the dream of many developers, including myself. Everything is asynchronous, decoupled, and scalable. What’s not to love? Well, a year ago, my dream came true. Finally, I could work on enterprise-scale messaging, microservices, NoSQL, IaC, and all in the cloud, of course.

Unfortunately, my dream slowly turned into a nightmare.

Event-driven architecture is like a dragon: immensely powerful but hard to tame. In this session, we look past its utopian ideas and explore its rugged reality.

We discuss the challenges I personally had to face when adapting to EDA and how I solved them. It’s about the hard parts you hope you never encounter but inevitably will when working in EDA systems: out-of-order messages, scheduling, versioning, and interacting with legacy systems.

After this session, you will be much better prepared than I was—prepared to work with event-driven architecture. Prepared to tame the dragon!