Socket.IO Rooms: Broadcasting to Subsets of Clients

Why it exists

Broadcasting an event to every single connected client is often too broad and inefficient. Real-time applications need a way to send targeted messages to specific groups, like participants in a private chat or users following a particular stock, without manually managing complex lists of individual socket IDs.

The mental model

A Socket.IO Room is like a server-side mailing list for your clients. Instead of sending a message to every connected socket, you send it to a named list, and only the sockets that have "subscribed" (joined the room) will receive it. This is purely a server-side abstraction; the client doesn't know what lists it's on.

How it works

The default Socket.IO Adapter maintains two internal maps: one mapping each socket ID to a set of room names it has joined, and another mapping each room name to a set of socket IDs within it. When you call socket.join('my-room'), the server updates both maps. When you call io.to('my-room').emit(...), the server looks up 'my-room' in its map and sends the message to every socket ID in the corresponding set. Upon disconnection, a socket automatically leaves all rooms it was a part of.

When to use it

Use rooms whenever you need to broadcast to a subset of clients. A common pattern is creating a room per user ID to message all of a user's connected devices (e.g., laptop and phone). Another is creating a room per resource, like 'project:123', to send updates about that specific resource to anyone interested.

When not to use it

Do not use the default room implementation if you are running multiple Socket.IO servers. The default adapter is in-memory and is not shared between server instances. A message sent from server A to a room will only reach clients connected to server A. For scaled applications, you must use a shared adapter, like the official Redis Adapter, to synchronize room state across all servers.

One canonical example

A common use case is creating a private channel for each user to notify all their connected devices. On connection, the server identifies the user and joins their socket to a room named with their unique user ID.

io.on("connection", (socket) => {
const userId = getUserIdFromSocket(socket);
socket.join(userId);
});

Later, to send a private notification to that user on all their devices, you emit to their room:

io.to(userId).emit("new-message", { from: "server" });

This sends the event only to sockets that have joined the room corresponding to that userId.