rsocket-java
Reactor
Our great sponsors
| rsocket-java | Reactor | |
|---|---|---|
| 5 | - | |
| 2,335 | 332 | |
| 0.3% | - | |
| 4.1 | 0.0 | |
| about 2 months ago | - | |
| Java | Java | |
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rsocket-java
- RSocket – An alternative to gRPC with first-class browser support
-
Async Streams in WebAssembly with WasmRS
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
You might also checkout https://rsocket.io/
-
Server-Sent Events: the alternative to WebSockets you should be using
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).
[0]: https://rsocket.io/
[1]: https://github.com/omnistreams/omnistreams-spec
-
Woe be onto you for using a WebSocket
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].
[0]: https://github.com/omnistreams
[1]: https://iobio.io/2019/06/12/introducing-fibridge/
[2]: https://boringproxy.io/
[3]: https://rsocket.io/
[4]: https://news.ycombinator.com/item?id=27823109
Reactor
We haven't tracked posts mentioning Reactor yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
RxJava - RxJava – Reactive Extensions for the JVM – a library for composing asynchronous and event-based programs using observable sequences for the Java VM.
Mutiny - An Intuitive Event-Driven Reactive Programming Library for Java
Reactive Streams - Reactive Streams Specification for the JVM
pushpin - A proxy server for adding push to your API, used at the core of Fastly's Fanout service
reactor-core - Non-Blocking Reactive Foundation for the JVM
ServiceTalk - A networking framework that evolves with your application
FluidFramework - Library for building distributed, real-time collaborative web applications
zotonic - Zotonic - The Erlang Web Framework & CMS
mod_sse - Zotonic module implementing Server Sent Events