Examples in using RedisStore in socket.io

by

but I don’t understand how using RedisStore in that code would be any different from using MemoryStore. Can someone explain it to me?

The difference is that when using the default MemoryStore, any message that you emit in a worker will only be sent to clients connected to the same worker, since there is no IPC between the workers. Using the RedisStore, your message will be published to a redis server, which all your workers are subscribing to. Thus, the message will be picked up and broadcast by all workers, and all connected clients.

Also what is difference between configuring socket.io to use redisstore vs. creating your own redis client and set/get your own data?

I’m not intimately familiar with RedisStore, and so I’m not sure about all differences. But doing it yourself would be a perfectly valid practice. In that case, you could publish all messages to a redis server, and listen to those in your socket handler. It would probably be more work for you, but you would also have more control over how you want to set it up. I’ve done something similar myself:

// Publishing a message somewhere
var pub = redis.createClient();
pub.publish("messages", JSON.stringify({type: "foo", content: "bar"}));

// Socket handler
io.sockets.on("connection", function(socket) {
  var sub = redis.createClient();
  sub.subscribe("messages");
  sub.on("message", function(channel, message) {
    socket.send(message);
  });

  socket.on("disconnect", function() {
    sub.unsubscribe("messages");
    sub.quit();
  });
});

This also means you have to take care of more advanced message routing yourself, for instance by publishing/subscribing to different channels. With RedisStore, you get that functionality for free by using socket.io channels (io.sockets.of("channel").emit(...)).

A potentially big drawback with this is that socket.io sessions are not shared between workers. This will probably mean problems if you use any of the long-polling transports.

More Related Contents:

  1. How to reuse redis connection in socket.io?
  2. How to share sessions with Socket.IO 1.x and Express 4.x?
  3. WebSockets and Apache proxy: how to configure mod_proxy_wstunnel?
  4. socket.io and session?
  5. nginx as webserver incl. socket.io and node.js / ws:// 400 Bad Request
  6. Differences between socket.io and websockets
  7. Socket.IO – how do I get a list of connected sockets/clients?
  8. How to display the lastmessage sent when user is not inside the chat?
  9. What is an example of the simplest possible Socket.io example?
  10. socket.io rooms or namespacing?
  11. Use socket.io inside a express routes file
  12. What’s the difference between io.sockets.emit and broadcast?
  13. Error: Redis connection to 127.0.0.1:6379 failed – connect ECONNREFUSED 127.0.0.1:6379
  14. How do I get a list of connected sockets/clients with Socket.IO?
  15. Node.js client for a socket.io server
  16. How to get room’s clients list in socket.io 1.0
  17. What is Express.js? [closed]
  18. Unit testing Node.js and WebSockets (Socket.io)
  19. how to list rooms on socket.io nodejs server
  20. Controlling the heartbeat timeout from the client in socket.io
  21. socket.io force a disconnect over XHR-polling
  22. Websocket transport reliability (Socket.io data loss during reconnection)
  23. Separating file server and socket.io logic in node.js
  24. How to resolve a Socket.io 404 (Not Found) error?
  25. Can I access a cookie from Socket.io?
  26. How to use socket.io in express routes?
  27. NPM – Can’t install socket.IO
  28. Socket.io rooms difference between broadcast.to and sockets.in
  29. How to connect two node.js servers with websockets?
  30. socket.io private message

Leave a Comment