Reactive for the Impatient
summary
Claims that reactive techniques tame asynchronicity by combining nonblocking streams, message-driven design and fault supervisors, and demonstrates actual Java toolchains: RxJava and Spring Reactor for streams, Akka for actor-based supervision and elasticity, and Vert.x for lightweight evented services. Shows marble-diagram code, a ramen-shop ordering prototype as a concrete example, notes backpressure works and that reactive DB drivers exist but most database engines still lack true nonblocking I/O.
AI-written summary · about
chapters (11)
- 0:00Intro
- 3:52Evolving changes/demands in the Computing Ecosystem
- 14:23Important distinctions...
- 17:44Event-Driven vs Message-Driven
- 19:33Reactive Programming: Patterns, Terminologies
- 21:53Rx Marble Diagram: Mapo
- 24:06Reactive Systems Design: Patterns, Terminologies
- 27:33What about Microservices?
- 30:56"Reactive" Design Thinking
- 39:58Spring 5: Spring Web Reactive (non-blocking web stack)
- 42:09Quick comparison: RxJava vs Spring Reactor
related talks
45mReactive for the Impatient - A Gentle Intro to Reactive Programming and Systems
52mReactive for the Impatient - A Gentle Intro to Reactive Java
39mReactive for the Impatient (A Gentle Intro to Reactive Java)
41mThe definite guide to reactive programming in Java
47mReactive Spring
32mThirst-Quenching Streams for the Reactive Mind
01h 21mReactive Web Applications
50mThe reactive landscape