RSocket - Future Reactive Application Protocol
summary
RSocket is a binary, message-driven protocol with Project Reactor bindings and a Spring Boot starter that claims 10x faster performance and far lower resource use than HTTP/1.1. It runs over TCP, WebSocket, HTTP/2, Aeron or QUIC, supports request/response, request-stream, fire-and-forget and bidirectional streaming, and exposes application-level flow control (reactive backpressure) plus resumeability for mobile handoffs, leasing-based rate limiting, fragmentation, and a broker spec for routing. Java and JavaScript libs are ready; other languages are progressing.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:36History of protocols
- 5:11Do we have today
- 6:40What do we need
- 11:28What is RSocket
- 13:10Binary Messaging
- 14:04Data Metadata
- 15:04Performance
- 16:39Flexibility
- 18:25Resilience
- 19:31Resilience Features
- 22:17PeertoPeer Communication
- 23:48Socket Java
- 29:24Testing
- 32:33Summary
- 33:56User Experience
- 34:50Disadvantages
- 36:02Process
- 36:47Conclusion
- 37:21RSocket Broker Specification
- 38:44Router Specification
- 39:56Micro Network
- 40:23Questions
related talks
01h 01mThe RSocket Protocol — The Future of Reactive Applications
40mReactive message driven service 2 service communication with RSocket
53mRSocket - future Reactive Application Protocol?
28mGetting Started With RSocket
40mRSocket as a Wire Protocol
01h 52m100% Fast and Resilient Microservice with RSocket
01h 21mReactive Web Applications
27mEnabling real time collaboration with RSocket