RSocket (rsocket.io)
- initially developed by Netflix
- an implementation of Reactive Streams specification
- is an application protocol/network-level API protocol with framing, session resumption, and backpressure built-in that works over the network
- is transport agnostic (i.e. RSocket can be run over WebSockets, TCP, 2, and Aeron)
4 Communication Models
FireAndForget
This mode supports sending a request without sending a response message. It can be applied to scenarios, such as event tracking and log reporting. A response in these scenarios is not needed, and it does not matter if several requests are lost.
-model/7---application-layer/reactive-streams/reactive-socket-(rsocket)/fire-and-forget.png)
RequestResponse
The requestor sends a request, and the responder receives the request and returns a response. HTTP typically uses the
RequestResponsemode.
-model/7---application-layer/reactive-streams/reactive-socket-(rsocket)/request-response.png)
RequestStream
The requester sends a request, and the responder returns N responses. Conventional MQ typically uses the
RequestStreammode.
-model/7---application-layer/reactive-streams/reactive-socket-(rsocket)/request-stream.png)
RequestChannel
Create a channel context so both parties can send messages. IM is a typical
RequstChannelscenario.
-model/7---application-layer/reactive-streams/reactive-socket-(rsocket)/request-channel.png)