Retrofit Your Java App with a Reactive Flow Pipeline
summary
A working demo wires Kafka -> Akka Streams (Scala) -> custom RSocket connector -> Project Reactor (Java) -> Kafka, with a sources producer pushing ~1 record/sec via docker-compose. Backpressure propagates: the first processor only consumes when the downstream signals demand; random sleep on the second processor forces the first to pause. Built a custom Akka-to-RSocket connector because no official one exists, and the pipeline proves reactive streams backpressure end-to-end, though RSocket Java binds to Reactor and docs are sparse. Akka Streams, RSocket, Kafka
AI-written summary · about
chapters (5)
- 0:00Start
- 2:03Introduction
- 3:06Traditional Enterprise JVM Applications
- 7:26Solutions using the Reactive Approach
- 25:49Experience from Building The Pipeline
related talks
30mRetrofit Your Java App With a Reactive Flow Pipeline
38mRetrofit your Java App with a Reactive Flow Pipeline
27mRetrofit your Java App with a Reactive Flow
37mReactive Pipeline Talk
01h 01mThirst Quenching Streams for the Reactive Mind
41mBuilding Reactive Pipelines with Kotlin & Spring
46mAkka Streams & Reactive Streams in action
01h 32mBuilding Reactive applications with Reactor and the Reactive Streams standard