How to Implement WebSockets in Node.js

Standard HTTP is a request-response protocol. The client sends a request and the server responds. The server cannot send data to the client without the client first making a request. For real-time features like live chat, notifications, or collaborative editing, this model requires constant polling which is wasteful and slow.

WebSocket is a protocol that establishes a persistent, full-duplex connection between the client and server over a single TCP connection. After an initial HTTP handshake to upgrade the connection, both the client and server can send messages to each other at any time without waiting. This enables true real-time communication with very low latency.

Install the socket.io package. Create an HTTP server using Node's built-in http module wrapping your Express app. Pass this HTTP server to Socket.IO's Server constructor rather than attaching Socket.IO to Express directly. This is required because WebSocket connections upgrade from HTTP, so Socket.IO needs access to the underlying HTTP server.

Call io.on and listen for the connection event. The callback receives a socket object representing the individual client connection. Every client that connects triggers this callback with its own unique socket. Inside the callback, you have access to the socket's ID, can listen for events from that specific client, and can emit events back to them.

Use socket.emit to send a named event with data to a specific client. Use socket.on to listen for a named event from that client. Define your own event names relevant to your application such as 'chat message', 'user typing', or 'score update'. Both the event name and the data payload are completely customizable.

Use io.emit to send an event to every connected client simultaneously. Use socket.broadcast.emit to send to all clients except the one who triggered the action. For example, when a user sends a chat message, the server receives it through socket.on and then broadcasts it to all other clients so everyone sees the new message in real time.

Rooms allow you to group sockets so you can send messages to specific subsets of clients. Call socket.join with a room name to add a socket to a room. Call io.to with the room name and then emit to send a message only to sockets in that room. Use rooms to implement features like chat channels, game lobbies, or per-document collaboration in editors.

Listen for the disconnect event on each socket to detect when a client closes the connection or loses network access. Inside the disconnect handler, clean up any state associated with that client, such as removing them from an active users list or notifying other clients in a room that the user has left. Always clean up resources on disconnect to prevent memory leaks over time.