The Promise of Event Driven Programming with Fast Data
summary
Reactive systems combine Akka actors, Kafka as a streaming backplane and Spark for analytics to implement event sourcing and closed‑loop feedback control across microservices that must own their own data. Claims: 21,000+ Reactive Manifesto signers; clustering for resilience and polyglot persistence for autonomy; avoid using the stream as the single source of truth. Practical pieces: supervisory control for self‑healing, split‑brain resolver, telemetry (Cinnamon), and tradeoffs between CRUD and event‑sourced models driven by SLAs.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:45About Us
- 5:08Outline
- 5:48Micro Services
- 14:52Promise Theory
- 18:06Event Sourcing
- 21:53Fast Data
- 27:01Feedback Control
- 34:55Building Systems
related talks
39mThe Promise of Event Driven Programming with Fast Data
54mReacting to an Event-Driven World
54mHow Events Are Reshaping Modern Systems
27mFour Principles of Reactive Architectures
17mKeynote: Is it Reactive or Eventful? Aren't they the Same?
50mAddressing Recent Events
31mFUNCTIONAL EVENT-DRIVEN ARCHITECTURE
47mThe Rise of Reactive Microservices