Application protocol providing Reactive Streams semantics. It is a binary protocol for use on byte stream transports such as TCP, WebSockets, and Aeron.
Need to stream lots of data quickly and don't need a guarantee that all of it arrives at its destination? Check out RSocket's fire-and-forget interaction model:
buff.ly/2G0d0B1
You will find many use cases for the request-stream interaction model in @RSocketIO. Check out this example to get you thinking on how you might be able to use it.
buff.ly/2RmNQSG
With Alibaba, Pivotal and Lightbend on board, Reactive flexes its ROI muscle in the microservices world | TechCrunch
"Goodbye HTTP, hullo Reactive"
#Reactive @lightbend @RSocketIOtechcrunch.com/2019/10/15/wi…
"The network is the unsolved problem of the cloud."
Good piece on reactive programming. Thanks to @netifi_inc and the rest of us, @RSocketIO is a great component of the stack.
This is the impetus behind us pushing the adoption of @RSocketIO. The jump to microservices left behind many great learnings from the networking world. We are bringing that back to the application layer with @RSocket and @netifi_inc
gRPC and @RSocketIO often get compared to each other, but as @rroeserr effectively lays out, they are quite different.
This post goes into OSI layer, client/server interaction, flow control, developer APIs, and lots more ... medium.com/netifi/difference…
.@RSocketIO allows us to take reactive beyond the application and onto the network, while @r2dbc allows to us extend reactive to persistent storage. @smaldini at #SpringOne