socket.io-redis | Using redis pubsub to push messages via socket | Socket library

I am working on setting up socket.io in cluster mode using PM2.

I am using socket.io-redis package and it works fine in cluster mode.

But the problem arises when I want to access all connected sockets. Because processes don't know about socket connections in other processes in cluster mode.

I thought socket.io-redis keeps track of all the connected sockets and all its session info but it didn't. Is there any way or solution to access all the socket connection existing in all processes in socket.io/Nodejs?

I'm using socket.io "^1.7.1", and "socket.io-redis": "^6.0.1" when I am doing the following

When using SocketIO in an application that runs behind a node-balancer, the official documentation states the way to pass events between those nodes (using SocketIO-Redis):

I am trying to play around with socket.io and figure out if it suits us. I have ran into a problem while trying stuff out.

so in my server i have the following code:

I have a VPC with 2 public subnets in different availability zones (public subnet-2a and public-subnet-2b). I have two private subnets (private-2a-EB-Instance, private-2b-EB-Instance), and two other private subnets for Elasticache (private-2a-EB-Instance, private-2b-EB-Instance), these two subnets for elasticache are part of a subnet group that I use when creating my Elasticache clusters.

I have create a security group for my ElastiCache(redis) and I have changed its inbound rules so it can accept connection from the security group of my ElasticBeanstalk environment. Didn't solve the problem.

I have followed the instructions on AWS' website, and I can't get it to work. I wonder what I am doing wrong. I am using socket-io-redis and I am wondering if that may be part of the problem.

I have used the .config file offered here , but I get an error when deploying the app. It says there was an error creating it.

I created the cluster from the console and tried to connect it to my EB app using the "Primary Endpoint", but I get the error:

I'm trying to build a realtime (private) chat between users of a video game with 25K+ concurrent connections. We currently run 32 nodes where users can connect through a load balancer. The problem I'm trying to solve is how to route messages to each user?

Currently, we are using socket.io & socket.io-redis, where each websocket joins a room with its user ID, and we emit each message they should receive to that room. The problem with this design is that we are reaching the limits of Redis Pubsub, and Socket.io which doesn't scale well (socket.io emit messages to all nodes which check if the user is connected, this is not viable).

Our current stack is composed of Postgres, Redis & RabbitMQ. I have been thinking about this problem a lot and have come up with 3 different solutions :

• Route all messages with RabbitMQ. When a user connects, we create an exchange with type fanout with the user ID and a queue per websocket connection (we have to handle multiple connections per user). When we want to emit to that user, we simply publish to that exchange. The problem with that approach is that we have to create a lot of queues, and I heard that this may not be very efficient.
• Create a queue for each node in RabbitMQ. When a user connects, we save the node & socket ID in a Redis Set, so that when we have to send a message to that specific user, we first get the list of nodes, emit to each node queue, which then handle routing to specific client in the app. The problems with that approach is that in the case of a node failure, we may store that a user is connected when this is not the case. To fix that, we would need to expire the users's Redis entry but this is not a perfect fix. Also, if we later want to implement group chat, it would mean we have to send duplicates messages in Rabbit, this is not ideal.
• Go all in with Firebase Cloud Messaging. We have a mobile app, and we plan to use it for push notifications when the user isn't connected, but would it be a good fit even if the user is connected?

What do you think is the best fit for our use case? Do you have any other idea?

I'm building a web server in nodejs which relies on redis, postgresql and mongodb. I store all the credentials in the google cloud secret manager, so I have to use asynchronous functions to get them. My code so far:

Im experimenting abit with Socket.io and Socket.Io-redis. I have my Redis server up and running. The error i get when starting the Socket.Io server is: ReplyError: ERR unknown command 'pubsub' I dont know why i get this error at all.

The Redis version i'm using is 2.4.5

I have just initialized a new project with Node.js and trying making the scripts in package.json file to be working.

For example I have the next package.json file: