Retrofit your Java App with a Reactive Flow Pipeline
summary
Shows how to wrap two legacy processors — one Scala using Akka Streams, one Java exposing an RSocket server — with Kafka topics to form a reactive flow pipeline. Demo publishes one message/sec, some items take 5s to process, and backpressure propagates upstream so the first processor stalls until the slow item finishes. Code uses Kafka, Akka, RSocket and Reactor; demo successfully proves a thin reactive shell protects slow legacy services while noting RSocket/Java integrations and Reactor idioms are still rough.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:07Agenda
- 2:21Fabios introduction
- 3:09Fabio introduction
- 4:00Why Reactive
- 6:39Complex Systems
- 7:48Reactive Systems
- 11:34Test Case
- 11:51Reactive Pipeline
- 13:57Legacy Processor
- 18:30Demo
- 22:39Experience
- 24:53Our Socket
- 27:22Conclusion
- 29:52Serverless
- 31:07Project Loom
- 33:26Will Project Loom replace Reactive
- 34:48Resources
related talks
27mRetrofit your Java App with a Reactive Flow
34mRetrofit Your Java App with a Reactive Flow Pipeline
37mReactive Pipeline Talk
41mBuilding Reactive Pipelines with Kotlin & Spring
53mGetting into the Flow: building applications with Reactive Streams
47mReactive Spring
01h 01mThirst Quenching Streams for the Reactive Mind
56mThirst-quenching Streams for the Reactive Mind
