Flashback to the early 2000s erstwhile SMS was the hot fresh thing – expensive, yet super exciting. Young and ambitious Manfred set out on an adventure that many called bold (and any 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 all day, for an affordable subscription fee.
But here's where it got interesting: Manfred didn't have a fancy dev server or a large budget for his backend. So of course all improvement was done in production. There he crafted a thin and mean strategy utilizing Windows Services, async communication, and Microsoft MessageQueue to handle the messaging magic. small did he know, his architecture had a fancy name: SEDA (Staged Event-Driven Architecture).
Fast forward nearly 20 years, and event-driven architecture is inactive the talk of the town. So why is this old dog learning fresh tricks all over again? Has much changed? And if it's so "cool," why aren't more people actually utilizing it?
In this light-hearted session, we’ll dive back into Manfred’s first plan and contrast it with today's "new" event-driven approaches. We'll research why this method is inactive relevant, its interactions with Master Data Management, data ownership, and data lineage. No hotel booking strategy examples here; we're all about fresh, applicable insights.
Stick around till the end for a playful live demo where microelectronics meet chaos – due to the fact that why not? Manfred, the ever-enthusiastic nerd, promises any controlled (and fun) madness.
DevOpsDays Warsaw: https://devopsdays.pl/
