From Functional to Reactive Programming
summary
Argues that reactive = functional++: start with functional composition and lazy streams, then add back pressure and three channels (data, error, complete). Shows Java examples (streams vs Flowable/Reactive Streams), using emit/subscribe, observeOn(Schedulers.io), and backpressure strategies drop or buffer to handle faster producers. Points to real systems — Excel, Google Docs, Kafka, AWS Lambda — and cites a customer case of ~70 million users in 48 hours to justify elasticity and message‑driven design.
AI-written summary · about
chapters (15)
- 0:00Introduction to Reactivity
- 1:00Functional Programming Roots
- 5:53Revisiting Paradigm Shifts
- 11:17Lists vs. Streams
- 15:20Understanding Lazy Evaluation
- 22:10Efficiency and Deadlines
- 26:28What is Reactive Programming?
- 28:46Real-world Reactive Examples
- 31:43Moving Beyond CRUD
- 36:20Pillars of Reactive Systems
- 42:50Resilience in Applications
- 49:03Implementing Reactive Streams
- 51:10Java Streams vs. Reactive
- 52:30Handling Errors and Backpressure
- 56:57Conclusion and Summary
related talks
01h 28mIntroduction to Reactive Programming
24mBringing Reactive Programming to Java and Microservices
41mThe definite guide to reactive programming in Java
52mReactive Programming in Java
41mFrom Imperative To Reactive
45mReactive for the Impatient - A Gentle Intro to Reactive Programming and Systems
56mThirst-quenching Streams for the Reactive Mind
52mReactive for the Impatient - A Gentle Intro to Reactive Java
