SocketCluster VS uWebSockets

SocketCluster mentions (7)

• Backpressure explained – the resisted flow of data through software

  I wrote an async/await stream library for JavaScript/Node.js which supports backpressure management. It's heavily tested and used as part of SocketCluster (pub/sub SDK) https://socketcluster.io/. - Source: Hacker News / 25 days ago

• Is it a good practice to store web sockets connections on redis?

  If redis doesn't satisfy your requirements or you're unable to make it work using adaptor, SocketCluster is a great package for this https://socketcluster.io/. Source: 10 months ago

• Why messaging is much better than REST for inter-microservice communications

  Interesting how this feature set is pretty much exactly the same as offered by SocketCluster https://socketcluster.io/. - Source: Hacker News / about 1 year ago

• On the Unhappiness of Software Developers

  This resonates with me 100%. Every bit of unhappiness I've felt in my career so far has been caused by a bad manager. The main issue for me has been the final point you mentioned about "Imposed artificial limitations" - I cannot tell you the number of times that I've been forced to use an inefficient tool or do something in a sub-optimal or downright incorrect way (knowing that it would have to be re-written... - Source: Hacker News / over 1 year ago

• Looking for real-time message solution recommendations

  The two best lightweight solutions I have worked with are SocketCluster and NATS. SocketCluster is used to build out a custom backend that scales very well. NATS would be used as a central pub/sub system. If you need queueing, you'll need to add additional services like Redis. Source: almost 2 years ago

uWebSockets mentions (0)