Socket.io architecture/configuration to connect to the closest server (GA) when it becomes available after the client has connected

Question

We have Global Accelerator setup in Amazon to route requests to the closest node (EC2) from some multiple nodes.

How does socket.io play out in this case? If let's say a user connected, and the socket client is connected to host A, but then host B which is closer, becomes available, is there some way for the socket requests to be routed through this closest server?

The typical scenario would be that if for some reason host B is overloaded and the Accelerator just routes the socket client to use host A at the time, but now the user is stuck on the distant server until he refreshes his page.

Thanks

Answer

Hello!

Unfortunately, this is a socket.io issue rather than an AWS one. Socket.io is a specific TCP connection between a client 
and a server. To switch hosts with socket.io you must disconnect from host A and reconnect to host B.

Any traffic routed without reconnecting will always go through host A until you disconnect and connect to another
host.

I would suggest looking for a different architecture if you desire this functionality.

Hope this helps!

Socket.io architecture/configuration to connect to the closest server (GA) when it becomes available after the client has connected

Relevant content