Event-Driven Architecture: Unleashing responsiveness
summary
Argues that cloud economics make event streams practical and shows a concrete pattern spectrum: event notification, delta events, state events and specifically include previous and latest state in the event so consumers can compute diffs without owning the domain. Uses Apache Kafka as the streaming layer and mentions stream processing with Apache Flink. Claims this reduces physical and temporal coupling, enables independent testing and scaling, and turns data into a first‑class, reusable asset (examples: shopping cart, stock price, cricket score).
AI-written summary · about
chapters (10)
- 0:00Event-driven concepts
- 1:51Defining events
- 3:58Synchronous vs event-driven
- 7:14Business adoption reasons
- 8:18Drawbacks of synchronous
- 11:47Testing and scaling
- 13:12Handling change
- 14:17Event-driven patterns
- 20:21Data orientation advantages
- 22:10Q&A
related talks
31mDemystifying Event-Driven Architectures
48mEvent-Driven Architecture – Benefits and Pitfalls
17mOvercome By Events - Apache Kafka And Event-oriented Architecture
01h 00mReacting to an Event-Driven World
27mKeynote II: Kafka and the Rise of Event-Driven Microservices
05mPREVIEW: Event-Driven Services with Stateful Streams
41mGetting started with Event-Driven Architectures in 2023
26mEvent Driven APIs
