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.

Components

Three Scaling Building Blocks

Pick the right component for your scaling story.

Load Balancer Server

Distribute WebSocket and HTTP connections across a pool of backup servers using random or fewest-connections algorithms. Backup servers auto-register their bindings.

WebSocket Proxy Server

Bridge browser WebSocket clients to any plain TCP/IP backend. Lets browsers virtually connect to legacy services that don't speak WebSocket natively.

HTTP API Server (HTTP.SYS)

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.

Why

Built for High-Concurrency Production

Each scaling component drops in next to standard sgcWebSockets servers and clients.

Pick Your Topology

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.

Add or remove backup servers without touching client config
Auto-restart watchdog reconnects backup servers to the load balancer
HTTP.SYS supports WebSockets (Win 8+), HTTP/1.1 and HTTP/2 (Win 2016+)
Proxy Server bridges browsers to any TCP backend