Keynote: Is it Reactive or Eventful? Aren't they the Same?
summary
Argues that reactive and event-driven systems largely overlap but differ in level — reactive as a higher‑level abstraction of goals (responsiveness, elasticity, resiliency, message‑driven) while event systems focus on mechanisms like event streaming and message queuing. Cites using Apache Pulsar for event streaming, data pipelines and serverless/microservices patterns, and a pharmaceutical proof‑of‑concept that streams blood‑sugar device events to notify caregivers. Highlights adoption, tooling, security and observability as the main blockers.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:41Reactive systems defined
- 3:26Reactive data handling
- 4:50Event-driven computing
- 6:55Reactive event-driven systems
- 8:20Reactive vs event-driven
- 10:25Human-like async interactions
- 11:52Adoption challenges
- 13:55Healthcare event-driven benefits
related talks
41mThe Promise of Event Driven Programming with Fast Data
27mKeynote II: Kafka and the Rise of Event-Driven Microservices
54mReacting to an Event-Driven World
49mRethinking Reactive Architectures
52mEvent-driven vs event sourcing: what's really the difference?
03mAm I only streaming? Thinking reactive
51mComplex Event Flows in Distributed Systems
54mHow Events Are Reshaping Modern Systems