This is basically the principle behind https://socketcluster.io/ scalability; the sharding of channels across available brokers is pseudo-random. It uses a hash function for determinism but the distribution looks essentially random. - Source: Hacker News / about 1 month ago

I started building something pretty obscure about 14 years ago; https://socketcluster.io/ an open source, WebSocket-based RPC + pub/sub library with a focus on in-order async stream-processing with backpressure monitoring. It didn't start out like that. Initially, it was just another WebSocket library with a focus on making it easier to scale to multiple processes. It's kind of mind-bending to me though that it... - Source: Hacker News / about 2 months ago

I've been advocating for this approach for years. You can't avoid race conditions without using some kind of queueing mechanism and you need backpressure to measure queue capacity. I built this into every aspect of https://socketcluster.io/ - From pub/sub channels, RPCs to event listeners. - Source: Hacker News / about 2 months ago

It's interesting reading this. Preventing these kinds of concurrency issues is exactly why I built https://socketcluster.io years ago. Though it solves the problem at the app layer rather than the storage layer. But not many developers care about these race conditions it seems. It's not just an issue with SQL but a more general issue with coding. This is a great example because it shows how concurrent executions... - Source: Hacker News / 2 months ago

Https://socketcluster.io/ has had such stream implementation and backpressure management since at least 2019;. https://github.com/SocketCluster/writable-consumable-stream. - Source: Hacker News / 5 months ago

Along with the reconnect solution already mentioned, you can also decouple your Websocket and business logic layers using something like Pushpin: https://pushpin.org/. This allows you to deploy your business logic layer without disconnecting/reconnecting clients. - Source: Hacker News / over 1 year ago

For realtime, I used Pushpin with Server Sent Events. (It supports WebSocket as well). - Source: dev.to / about 3 years ago

Instead of letting clients directly interface with your services over websockets, consider using Pushpin [1], which allows you to completely isolate realtime communication from your services. As a bonus, it also provides you the ability to cycle (redeploy/restart) your services without your clients having to reconnect (that's where the name comes from). And as you can imagine - because communication with your... - Source: Hacker News / about 3 years ago

Vapor[0] based on Swift. Advantage of this is that you don't have to evaluate multiple frameworks for Swift and suffer paralysis by analysis. All the Swift community is behind one framework. The next is Actix[1] based on Rust. There are many frameworks in Rust and most of them have not reached 1.0 And which framework will survive becomes a question. Other not so well-known is Wt[2] based on C++. This actually is... - Source: Hacker News / over 3 years ago

If you are developing the backend then Pushpin[0] is the easiest to integrate with. [0] https://pushpin.org. - Source: Hacker News / over 3 years ago