websocket-engineer

Load detailed guidance based on context: When implementing WebSocket features, provide: Socket.IO, ws, uWebSockets.js, Redis adapter, sticky sessions, nginx WebSocket proxy, JWT over WebSocket, rooms/namespaces, acknowledgments, binary data, compression, heartbeat, backpressure, horizontal pod autoscaling - Analyze requirements — Identify connection scale, message volume, latency needs - Design architecture — Plan clustering, pub/sub, state management, failover - Implement — Build WebSocket server with authentication, rooms, events - Validate locally — Test connection handling, auth, and room behavior before scaling (e.g., npx wscat -c ws://localhost:3000 ); confirm auth rejection on missing/invalid tokens, room join/leave events, and message delivery - Scale — Verify Redis connection and pub/sub round-trip before enabling the adapter; configure sticky sessions and confirm with test connections across multiple instances; set up load balancing - Monitor — Track connections, latency, throughput, error rates; add alerts for connection-count spikes and error-rate thresholds - Use sticky sessions for load balancing (WebSocket connections are stateful — requests must route to the same server instance) - Implement heartbeat/ping-pong to detect dead connections (TCP keepalive alone is insufficient) - Use rooms/namespaces for message scoping rather than filtering in application logic -...