The Art and Benefits of Computing Eventfully
summary
Survey of eventful computing that names concrete tools and tradeoffs: Apache Pulsar and Kafka for ingestion, Flink/Pinot/StarTree for real‑time processing, BookKeeper/Zookeeper for durability, and Astra streaming and CDC for managed change capture. Claims: event sourcing stores immutable events for replay (used to trace trades), streaming processes in memory to cut ETL latency, and Pub/Sub can handle millions of messages/s. Benefits: real‑time fraud detection and reactive responsiveness; cost: harder tracing and ordering concerns and extra IO when microservices multiply.
AI-written summary · about
chapters (10)
- 0:00Introduction to eventful computing
- 6:58Defining events and their role
- 12:13Event sourcing and event storming
- 16:09Event-driven messaging techniques
- 21:03Event streaming vs batch processing
- 26:39Fundamental states of data
- 27:22Benefits of event-driven systems
- 34:47Microservices and modern architectures
- 38:18Streaming vs traditional data pipelines
- 40:05Summary and resources
related talks
27mLeveraging Event Streaming to Super-Charge your Business Solutions.
45mDeep dive into Unbounded Data Processing Systems
17mOvercome By Events - Apache Kafka And Event-oriented Architecture
23mEvent-Driven Architecture: Unleashing responsiveness
30mEvent Streaming and the Future of Applications
36mStream All The Things!
51mEvent Streaming and Processing with Apache Pulsar
31mFUNCTIONAL EVENT-DRIVEN ARCHITECTURE
