Help us improve the AWS re:Post Knowledge Center by sharing your feedback in a brief survey. Your input can influence how we create and update our content to better support your AWS journey.
Socket.io architecture/configuration to connect to the closest server (GA) when it becomes available after the client has connected
0
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.
