Scale socket.io with nodejs for 4000 concurrent connections.

• Socket.io

  826 60,129 7.8 TypeScript

  Realtime application framework (Node.JS server)

  

We are using nodejs for our backend code and socket.io library for real-time communication. Our server is deployed on an AWS EC2 instance. Currently, we are not able to scale more than 200 concurrent socket connections. How can we scale it? What is the best practice to implement socket.io for this scale?

• Redis

  318 64,821 9.7 C

  Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs, Bitmaps.

  

Ideally you'd want a load balancer in-front of your application and then route it to multiple redundant and stateless instances of your web application that would only relay information to the client using some sort of in-memory centralised data store, as an example setup.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• uWebSockets.js

  32 7,252 8.2 C++

  μWebSockets for Node.js back-ends :metal:

  

Try this instead: https://github.com/uNetworking/uWebSockets.js/

Suggest a related project