Demystifying Event-Driven Architectures
summary
Defines Event-Driven by showing concrete patterns and tools: uses Apache Kafka topics/log-backed logs, a producer that emits one event per second and three consumers that each receive the same event, and the consumer poll loop for retrieval. Argues for event sourcing to persist an append-only ledger, replay to rebuild materialized views, and accepts eventual consistency as the trade-off versus synchronous APIs. Recommends one producer type per topic to avoid coupling and illustrates hover-events driving recommendation pipelines.
AI-written summary · about
chapters (10)
- 0:00Event-driven architectures intro
- 2:01Monoliths vs microservices
- 6:17What is EDA?
- 9:51Understanding event streams in depth
- 15:48Eventual consistency trade-offs
- 16:09Commands, queries, events
- 23:49Apache Kafka demo
- 24:09Event-carried state transfer
- 26:16Event sourcing & views
- 30:11Closing & Q&A
related talks
48mEvent-Driven Architecture – Benefits and Pitfalls
23mEvent-Driven Architecture: Unleashing responsiveness
41mGetting started with Event-Driven Architectures in 2023
01h 00mReacting to an Event-Driven World
39mEvent Driven Architecture: From Ideation to Production
42mCreating event-driven microservices: the why, how and what
54mHow Events Are Reshaping Modern Systems
27mPatterns for Event-Driven APIs