Flashback to the early 2000s when SMS was the hot new thing – expensive, yet super exciting. Young and ambitious Manfred set out on an adventure that many called bold (and some called a bit foolish). He built a website where users could register, showcase their profiles, upload photos, and send a generous amount of SMS/MMS every day, for an affordable subscription fee.

But here's where it got interesting: Manfred didn't have a fancy dev server or a big budget for his backend. So of course all development was done in production. There he crafted a lean and mean system using Windows Services, async communication, and Microsoft MessageQueue to handle the messaging magic. Little did he know, his architecture had a fancy name: SEDA (Staged Event-Driven Architecture).

Fast forward nearly 20 years, and event-driven architecture is still the talk of the town. So why is this old dog learning new tricks all over again? Has much changed? And if it's so "cool," why aren't more people actually using it?

In this light-hearted session, we’ll dive back into Manfred’s original design and contrast it with today's "new" event-driven approaches. We'll explore why this method is still relevant, its interactions with Master Data Management, data ownership, and data lineage. No hotel booking system examples here; we're all about fresh, practical insights.

Stick around till the end for a playful live demo where microelectronics meet chaos – because why not? Manfred, the ever-enthusiastic nerd, promises some controlled (and fun) madness.

Come with questions, leave with answers (hopefully in that order), and maybe, just maybe, a bit of inspiration for your next project.