AS
выше постили статью https://dzone.com/articles/load-balancing-of-websocket-connections
где говорится :
> For a better understanding of WS load balancing let’s dive a bit deeper into TCP sockets background. By default, a single server can handle 65,536 socket connections just because it’s the max number of TCP ports available. So as WS connections have a TCP nature and each WS client takes one port we can definitely say that number of WebSocket connections is also limited.
Такое же было мое понимание и до статьи - т.к. Websocket это stateful TCP соединение - держит 1 порт, потолок портов у TCP 65536
где говорится :
> For a better understanding of WS load balancing let’s dive a bit deeper into TCP sockets background. By default, a single server can handle 65,536 socket connections just because it’s the max number of TCP ports available. So as WS connections have a TCP nature and each WS client takes one port we can definitely say that number of WebSocket connections is also limited.
Такое же было мое понимание и до статьи - т.к. Websocket это stateful TCP соединение - держит 1 порт, потолок портов у TCP 65536
