What Are WebSockets and How They Differ from HTTP Real-Time Communication Guide

What Are WebSockets?

WebSockets provide full-duplex, persistent communication between a client and server over a single TCP connection. Unlike HTTP, which is request-response, WebSockets allow the server to push data to the client at any time.

HTTP vs WebSockets

HTTP: Request-Response

Client: "Give me the latest messages"  →  Server: "Here are 10 messages"
Client: "Any new messages?"  →  Server: "No"
Client: "Any new messages?"  →  Server: "No"
Client: "Any new messages?"  →  Server: "Yes, here's one"

This is called polling wasteful and slow.

WebSocket: Full-Duplex

Client ↔ Server: Connection established (handshake)
Server: "New message from Jane!"  (pushed without client asking)
Client: "Thanks, I'll display it"
Server: "Another message from John!"  (pushed instantly)

No polling needed the server pushes data as soon as it's available.

The WebSocket Handshake

1. Client sends an HTTP request with Upgrade: websocket header
2. Server responds with 101 Switching Protocols
3. Connection upgrades from HTTP to WebSocket
4. Both sides can now send messages at any time

// Client (browser)
const ws = new WebSocket("ws://localhost:3000");

ws.onopen = () => {
  console.log("Connected");
  ws.send("Hello Server!");
};

ws.onmessage = (event) => {
  console.log("Received:", event.data);
};

Why Use WebSockets in Node.js?

1. Real-time chat Messages appear instantly
2. Live notifications Push alerts without polling
3. Collaborative editing Multiple users editing simultaneously
4. Live dashboards Real-time data updates
5. Gaming Low-latency bidirectional communication
6. Stock tickers Continuous price updates
7. Presence Online/offline status

WebSocket Alternatives

The Takeaway

WebSockets provide full-duplex, persistent communication the server can push data to the client without the client asking. This is essential for real-time features like chat, notifications, and live updates. Unlike HTTP's request-response model, WebSockets keep the connection open and have minimal overhead after the initial handshake. Use WebSockets for bidirectional real-time communication, SSE for one-way server pushes, and polling for simple, low-frequency updates.