A Tale of Two Monix Stream
summary
Monix v3 adds Cats integration and a new pull-based stream called Iterant, and contrasts two concrete implementations: push-based Observable with Ack backpressure that uses Tasks/Futures and complex, high-performance flatMap state machines, and pull-based Iterant with batched iterators that favors referential transparency, resource-safe short-circuiting and interpretable code. Benchmarks show Observable often yields higher throughput while batched Iterant narrows the gap; both speak Reactive Streams for interop. Implementation complexity and memory-safety trade-offs determine which to choose.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:28About Monix
- 3:11Observable
- 5:40Problems
- 6:49Protocols
- 10:57Observability
- 15:07Poolbase
- 16:21State Machines
- 19:45Scala
- 24:45Iterator
- 25:20Iterator vs observable
- 27:08Flatmap
- 27:57Benchmarks
- 28:27Runt
- 29:17ThirdRight
- 31:56Conclusion
- 32:37Reactive Streams
- 33:05Implementation
related talks
32mPRACTICAL REACTIVE STREAMS WITH MONIX
35mPractical Reactive Streams with Monix
56mThirst-quenching Streams for the Reactive Mind
49mThirst Quenching Streams for the Reactive Mind
55mDemystify the Reactive Jargons
01h 01mThirst Quenching Streams for the Reactive Mind
37mAkka & Monix: Controlling Power Plants
27mReactive Programming in Node
