SocketCluster VS Socket.io

SocketCluster Reviews

Socket.io Reviews

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 / 26 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

Socket.io mentions (716)

• Mastering Microservices: A Hands-On Tutorial with Node.js, RabbitMQ, Nginx, and Docker

  Before diving into this tutorial, if you find microservices mysterious, check out my previous article for a detailed explanation. In this hands-on tutorial, we'll build a real-time chat server using Node.js, Socket.io, RabbitMQ, and Docker. Get ready for a practical journey into the world of microservices! Let's begin. - Source: dev.to / 2 months ago

• WebSockets Unlocked: Mastering the Art of Real-Time Communication

  Now we will be implementing socket logic using socket.io for building websockets. This library provides an abstraction layer on top of WebSockets, simplifying the process of creating real-time applications. For better maintainability, it is recommended to create a separate file for socket calls. To do this, navigate to the src folder, create a folder named services, and inside it, create a file named socket.ts... - Source: dev.to / 3 months ago

• Socket io not working on deployed version

  Hi I made a chat app using socket.io it worked fine locally but when I deployed the app on render.com socket is not working properly I have to refresh the page to see new messages please help... Source: 4 months ago

• Hi guys, just wanted to share that I tried to create a better omegle alternative. Open to any feedback!

  Nextjs + socket.io.. Planning to use webrtc for video calls later. Source: 4 months ago

• Does the MERN app with socket.io work correctly in the Google app engine?

  I am using socket.io for real-time notification service. Previously my frontend part was deployed in Netlify and here the notification was not working properly as Netlify follows serverless architecture. Source: 4 months ago