Multi Service Reactive Streams Using Spring, Reactor, and RSocket
summary
RSocket carries Reactive Streams backpressure across the network so a remote publisher only materializes records the consumer requests, demonstrated with Spring Reactor code showing request-response, request-stream, fire-and-forget and channel interactions over WebSocket or TCP. The protocol adds metadata frames, fragmentation, leasing for server-directed load control and resumability to pick up missed frames; demos show symmetric client/server APIs and working Spring integration, with one brief demo hiccup but otherwise successful execution.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:10Why Reactive
- 1:50Reactive Programming Review
- 2:47Composite Health
- 3:36Reactive Everywhere
- 4:55RSocket
- 5:55What is RSocket
- 11:53Use Cases
- 14:23Reactive Streams
- 16:14Interaction Models
- 18:17Fire and Forget
- 20:13Request Stream
- 21:21Reactive Back Pressure
- 23:04Unstructured Channel
- 24:32OurSocket
- 30:24OurSocket Flexibility
- 34:21Programming Model Agnostic
- 42:27Whats Next
- 43:03Metadata
- 44:51Fragmentation
- 46:23Cancellation
- 47:12Leasing
- 48:55Resume
