How do Socket.IO rooms organize client communication?

WHAT ROOMS ARE

Rooms are a virtual grouping mechanism in Socket.IO. When you join a socket to a room, it becomes a member. You can then emit events to only that room, not to all clients globally. This solves the problem of selective broadcasting: send messages to users in a specific chat, notify players in a specific game lobby, or alert subscribers in a specific monitoring channel.

JOINING AND LEAVING

When a client connects, the socket joins a room by default using its own socket.id. You can explicitly join: socket.join('roomName'). A socket can join multiple rooms simultaneously. To leave: socket.leave('roomName'). Leaving is automatic on disconnect: the socket is removed from all its rooms.

EMITTING TO ROOMS

io.to('roomName').emit('eventName', data) sends a message to all sockets in the room. You can also chain methods: io.to('room1').to('room2').emit() sends to sockets in both rooms. The syntax io.in() is equivalent to io.to().

MULTI-CHANNEL CHAT EXAMPLE

A chat application has channels: general, engineering, marketing. When Alice joins the engineering channel, the server calls socket.join('engineering'). When Bob joins general, socket.join('general'). When Alice sends a message, the server emits: io.to('engineering').emit('message', { user: 'Alice', text: '...' }). Only Bob's general socket is unaffected.

STATE MANAGEMENT NOTE

Rooms exist in memory on the server instance. If you have multiple Node.js servers behind a load balancer, each server only knows about its local rooms. To synchronize room broadcasts across servers, use Socket.IO's adapter (Redis adapter is common), which broadcasts room messages through Redis to all servers.

COMMON PATTERNS

Private notifications: socket.join('user:' + userId), then io.to('user:123').emit() sends private messages. Presence tracking: user joins presence rooms, others query the room to see who is online. One-to-one communication: both sockets join a private room just for them.