rivalis VS SocketCluster

github link website link

Recently, I added an AI-generated soundtrack to my open source project's home page https://socketcluster.io/

It seems unconventional at first but I distinctly remember about a decade ago when Adobe Flash was still broadly supported, many Flash websites had soundtracks. I think the reason why regular HTML websites didn't have them was because it was difficult to implement and internet was much slower so they had to be streamed in a special way.

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/

Interesting how this feature set is pretty much exactly the same as offered by SocketCluster https://socketcluster.io/

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 later) by a bad manager... In some companies, it was a daily occurrence; that's why I never stayed at a single company for longer than 2 years. It's almost impossible to find a company that lets me implement things correctly.

Thankfully, nobody could constrain me in my open source work. I (with the help of community members) built:

- SocketCluster (https://socketcluster.io/): A distributed pub/sub framework.

- Capitalisk (https://capitalisk.com/): A lightweight quantum-resistant blockchain which is less than 5K lines of code.

- LDEX (https://ldex.trading/): A deterministic decentralized exchange (DEX) which can work with many different blockchain protocols. It's less than 4K lines of code in total and only has 3 small third-party dependencies (including sub-dependencies).

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.

In the homepage for SocketCluster it is mentioned that it is a Highly scalable pub/sub and RPC framework optimized for async/await. However in the documentation I have not found anything related to RPC. Am I interpreting anything wrong here?

At the time of writing, SocketCluster has almost 6k stars on GitHub and 7k downloads on npm weekly,

SocketCluster is a framework which allows you to use the WebSocket protocol the transmit between its backend API and client library. The client can be used both on a backend (E.g. a Raspberry pi) or frontend application.