Event Driven Architecture: From Ideation to Production
summary
Practical playbook for getting the first event into production: choose technology to match ops skills — using Event Hub with Kafka connectors when managed streaming is needed, or run a local Kafka Docker for dev; prototype events inside a monolith via the mediator pattern so producers and consumers are already modelled; try Axon + Atom feeds per producer to avoid a central stream while learning; add correlation IDs, consistent log formats, snapshot tuning (from 100 to 10 helped), contract tests and a platform stream for cross‑functional concerns.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:50Event Driven Architecture
- 4:18Microservices
- 7:10Agenda
- 10:07EventDriven Architecture
- 11:24Terms
- 16:19Anns experience
- 18:48Grouping events
- 22:40Testing
- 28:45Crossfunctional requirements
- 30:24Understanding performance
- 34:29Debugging
related talks
45mCommon quandaries implementing your first Event Driven Architecture
31mDemystifying Event-Driven Architectures
01h 08mEvent Driven Architecture – Enabling Microservices
23mEvent-Driven Architecture: Unleashing responsiveness
48mEvent-Driven Architecture – Benefits and Pitfalls
42mCreating event-driven microservices: the why, how and what
41mGetting started with Event-Driven Architectures in 2023
26mEvent Driven APIs
