Demystify the Reactive Jargons
summary
Benchmarks compare blocking I/O, Scala Futures and RxJava Observables running the same workload and measure throughput, latency and memory under identical load. Results show blocking calls saturate thread pools and increase tail latency, naive Futures spawn contention as concurrency rises, while Observables with backpressure keep steady memory and smoother throughput. A CLI that consumes the Twitter Streaming API demonstrates the patterns live and includes concrete code, runtime metrics and failure behavior so viewers can judge tradeoffs and reuse the exact approaches.
AI-written summary · about
chapters (8)
- 0:00Start
- 8:15Execution Context
- 20:35Demoing the Jdbc Scenario
- 35:22Error Handling
- 42:12Reactive Streams
- 43:07Summary
- 44:12Streaming Api
- 48:01Create a Domain Model
