An introduction to WebSockets and how to load balance them. WebSockets creates a responsive experience for end-users by creating a bi-directional communication stream versus the one-way HTTP ...
Hi!
Thank you for your article. It was interesting.
You would be able to use XFF for the first packet for the rest would be depending on the web sockets application right? You lose certain aspects as URI manipulation, cookie insertion in the load balancers too right? One more question about the scaling. If you'd patch servers wouldn't the connections be quite unbalanced after service interruption since they're so long lived? One of the benefit with short lived HTTP connections is that they're easily distributed. Can you achieve this with web sockets too somehow?
It seems useful, but I'd like to read more about the limitations too. I know Lori wrote some last year, but it's been a while now. :)
/Patrik