Java implementation of RSocket (by rsocket)

Rsocket-java Alternatives

Similar projects and alternatives to rsocket-java

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better rsocket-java alternative or higher similarity.

rsocket-java reviews and mentions

Posts with mentions or reviews of rsocket-java. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-11.
  • RSocket – An alternative to gRPC with first-class browser support
    1 project | | 9 Jan 2024
  • Async Streams in WebAssembly with WasmRS
    5 projects | | 11 Jan 2023
    TL;DR: WasmRS is an implementation of RSocket for WebAssembly giving you reactive, async streams in and out of WASM modules. GitHub | Protocol details | Rust source | Go source
  • Mark Nottingham: Server-Sent Events, WebSockets, and HTTP
    11 projects | | 19 Feb 2022
    You might also checkout
  • Server-Sent Events: the alternative to WebSockets you should be using
    19 projects | | 12 Feb 2022
    My personal WebSockets vs SSE TL;DR goes something like this:

    * If you're on HTTP/2, start with SSE

    * If you need to send binary data, use WebSockets

    * If you need fast bidi streaming, use WebSockets

    * If you need backpressure and multiplexing for WebSockets, use RSocket or omnistreams[1] (one of my projects).



  • Woe be onto you for using a WebSocket
    7 projects | | 22 Dec 2021
    A few years ago I was more inclined to use WebSockets. They're undeniably cool. But as implemented in browsers (thanks to the asynchronous nature of JavaScript) they offer no mechanism for backpressure, and it's pretty trivial to freeze both Chrome and Firefox sending in a loop if you have a fast upload connection.

    I designed a small protocol[0] to solve this (and a few other handy features) which we use at work[1]. A more robust option to solve similar problems is RSocket[3].

    More recently I've been working on a reverse proxy[2], and realized how much of a special case WebSockets is to implement. Maybe I'm just lazy and don't want to implement WS in boringproxy, but these days I advocate using plain HTTP whenever you can get away with it. Server Sent Events on HTTP/1.1 is hamstrung by the browser connection limit, but HTTP/2 solves this, and HTTP/3 solves HTTP/2's head of line blocking problems.

    Also, as mentioned in the article, I try to prefer polling. This was discussed recently on HN[4].






  • A note from our sponsor - SaaSHub | 20 May 2024
    SaaSHub helps you find the best software and product alternatives Learn more →


Basic rsocket-java repo stats
3 months ago

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives