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 update metadata at runtime in your @RSocketIO application? Check out how to use the metadata-push interaction model here:
https://t.co/TOjJUTk0Cv
Want to make sure your subscriber's don't miss a message with @RSocketIO? Check out this example of pairing RSocket with @ProjectReactor.
https://t.co/uhazWA4iuV
Need a bi-directional communication channel for your microservices or apps? Check out the channel interaction model in RSocket.
https://t.co/pabU3PvrZH
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:
https://t.co/O8qcUQKN2A
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.
https://t.co/fKBB2aWFhW
With Alibaba, Pivotal and Lightbend on board, Reactive flexes its ROI muscle in the microservices world | TechCrunch
"Goodbye HTTP, hullo Reactive"
#Reactive @lightbend @RSocketIO
https://t.co/piRxLQFEll
"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 ... https://t.co/GkBbaQQb1W
.@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