My situation is that we currently write an online application which uses Node.js on server side with WebSocket listener. We have two different parts: one serves pages and uses node.js and express+ejs, another is a completely different app which only includes socket.io library for websockets. So here we come to this issue of scalability of websockets part.
One solution we've found is to use redis and share sockets information among servers, but due to architecture it will require sharing of loads of other information, which is going to create huge overhead on servers.
After this intro, my question is - is it possible to use cookie based load balancing for websockets? So that lets say every connection from user with cookie server=server1 will always be forwarded to server1 and every connection with cookie server=server2 will be fw to server2 and connection with no such cookie will be fw to least busiest server.
UPDATE: As one 'answer' says -- yes, i know this exists. Just did not remember that name is sticky session. But the question is -- will that work for websockets? Are there any possible complications?