Reactive message driven service 2 service communication with RSocket
summary
RSocket is a bi-directional multiplexed binary protocol that runs over TCP, WebSocket or Aeron and implements four interaction models: fire-and-forget, request-response, request-stream and channel. The demo uses Java Reactor APIs, shows frame-level hex on TCP, streaming with built‑in backpressure and a resume feature that caches frames for reconnects. Metadata frames allow schema hints; client-side load balancing and protobuf/RPC libraries exist. Current releases are pre‑1.0 (0.12) and recommended for POCs, not critical production.
AI-written summary · about
chapters (18)
- 0:00Introduction and announcements
- 1:51Microservices communication challenges
- 4:29Payment system architecture example
- 7:27Why switch from HTTP and gRPC
- 8:12RSocket protocol overview
- 11:23RSocket multiplexing explained
- 12:50Reactive streams and backpressure
- 13:56RSocket interaction models
- 15:18Live API demo introduction
- 18:40Demo fire-and-forget example
- 20:44Demo request-response model
- 21:51Demo streaming and cancellation
- 22:16Demo backpressure mechanism
- 24:09RSocket features for cloud use
- 28:26Low-level vs high-level APIs
- 30:15RSocket summary and takeaways
- 31:46Production readiness and future
- 32:10Q&A session begins
related talks
42mRSocket - Future Reactive Application Protocol
53mRSocket - future Reactive Application Protocol?
01h 52m100% Fast and Resilient Microservice with RSocket
01h 21mReactive Web Applications
53mMultiplayer Pac-Man with RSocket
39mConnect IoT with RSocket
42mReactive applications with WebSockets
01h 01mReactive web services