Scaling Components
Run your sgcWebSockets deployment across many instances. Distribute connections behind a load balancer, bridge browsers to legacy TCP servers, or switch to a kernel-mode HTTP.SYS acceptor for maximum concurrency on Windows.
Run your sgcWebSockets deployment across many instances. Distribute connections behind a load balancer, bridge browsers to legacy TCP servers, or switch to a kernel-mode HTTP.SYS acceptor for maximum concurrency on Windows.
Pick the right component for your scaling story.
Skaluj serwery WebSocket na wielu węzłach. Zdarzenie publikacji lub Presence na jednym węźle dociera do subskrybentów na każdym innym węźle, poprzez mesh bez infrastruktury lub backplane Redis.
Distribute WebSocket and HTTP connections across a pool of backup servers using random or fewest-connections algorithms. Backup servers auto-register their bindings.
Bridge browser WebSocket clients to any plain TCP/IP backend. Lets browsers virtually connect to legacy services that don't speak WebSocket natively.
Use the kernel-mode Microsoft HTTP Server API as the transport. Built-in WebSockets, HTTP/1.1, HTTP/2 and SSL support. Port-share with IIS on the same Windows host.
Przełącz serwer WebSocket Indy na porty uzupełniania I/O systemu Windows. Obsługuj tysiące jednoczesnych połączeń z małą pulą wątków zamiast jednego wątku na połączenie.
Przełącz serwer WebSocket Indy na epoll systemu Linux. Skaluj do tysięcy jednoczesnych połączeń w systemie Linux z ograniczoną pulą wątków.
Each scaling component drops in next to standard sgcWebSockets servers and clients.
Run a pool of TsgcWebSocketHTTPServer instances behind a TsgcWebSocketLoadBalancerServer for horizontal scale-out. Switch a single-machine deployment to TsgcWebSocketServer_HTTPAPI to take advantage of kernel-mode I/O completion ports and port-share with IIS. Or expose a TCP-only backend to browser WebSocket clients with TsgcWebSocketProxyServer.