Hacker News Reader

Socket.io has a great article on how you can setup your architecture to scale Web Socket servers: https://socket.io/docs/v4/using-multiple-nodes/

View on HN

The whole article seems to be about sticky sessions which are needed for the long polling fallback transport option Socket.io uses when websockets can't be used.

Eg. from the article: " the WebSocket transport does not have this limitation, since it relies on a single TCP connection for the whole session. Which means that if you disable the HTTP long-polling transport (which is a perfectly valid choice in 2021), you won't need sticky sessions "

>since it relies on a single TCP connection for the whole session.

still has to exist and stay active. (ie, interact with the correct node)

Reply on news.ycombinator.com