I am trying to implement a zero downtime socket.io cluster environment in NodeJS.
My goal is to distribute the server load in multiple node instances using Redis to sync data.
I was wounding if its possible, once a new change is detected, to make the socket.io client's reconnect on another instance without any down time or data loss.
To resume my idea, my goal would be to reload socket.io with new code without any downtime.
If this is a restful webservice this shouldn't be an issue. If you load balance your NodeJS servers and all the servers are connected to the same redis instance or cluster then when you gracefully pull a server out of your load balancers rotation there should be no noticeable downtime for your clients. Really this methodology would work for any environment.