Broadcasting messages in NestJS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output when broadcasting a message to all connected clients?

Consider a NestJS WebSocket gateway that broadcasts a message to all connected clients using this.server.emit('message', data). What will the clients receive?

NestJS

import { WebSocketGateway, WebSocketServer } from '@nestjs/websockets';
import { Server } from 'socket.io';

@WebSocketGateway()
export class ChatGateway {
  @WebSocketServer()
  server: Server;

  broadcastMessage(data: string) {
    this.server.emit('message', data);
  }
}

A All connected clients receive the 'message' event with the data.

B Only the client that sent the last message receives the broadcast.

C No clients receive the message because emit is not a broadcast method.

D Only clients in a specific room receive the message.

💡 Hint

Think about how emit works on the server instance in Socket.IO.

Using this.server.emit sends the event to all connected clients, broadcasting the message globally.

❓ state_output

intermediate

What is the state of connected clients after broadcasting?

In a NestJS WebSocket gateway, after calling this.server.emit('update', payload), what happens to the list of connected clients?

NestJS

import { WebSocketGateway, WebSocketServer } from '@nestjs/websockets';
import { Server } from 'socket.io';

@WebSocketGateway()
export class UpdateGateway {
  @WebSocketServer()
  server: Server;

  sendUpdate(payload: any) {
    this.server.emit('update', payload);
  }
}

A Clients are disconnected automatically after receiving the broadcast.

B The list of connected clients is cleared after broadcasting.

C The list of connected clients remains unchanged after broadcasting.

D Only clients that received the update remain connected.

💡 Hint

Broadcasting sends messages but does not affect client connections.

Broadcasting messages does not change the connection state of clients; all remain connected unless explicitly disconnected.

📝 Syntax

advanced

Which option correctly broadcasts a message to a specific room?

Given a NestJS WebSocket gateway, which code snippet correctly broadcasts a message only to clients in the room 'chat-room'?

NestJS

import { WebSocketGateway, WebSocketServer } from '@nestjs/websockets';
import { Server } from 'socket.io';

@WebSocketGateway()
export class RoomGateway {
  @WebSocketServer()
  server: Server;

  broadcastToRoom(message: string) {
    // Which option is correct here?
  }
}

A this.server.emit('chat-room', 'message', message);

B this.server.to('chat-room').emit('message', message);

C this.server.in('chat-room').broadcast.emit('message', message);

D this.server.broadcast.to('chat-room').emit('message', message);

💡 Hint

Use the Socket.IO method to target a specific room.

The to method targets a room, and emit sends the event to that room's clients.

🔧 Debug

advanced

Why does broadcasting fail with 'this.server.broadcast.emit'?

In a NestJS WebSocket gateway, a developer tries to broadcast a message using this.server.broadcast.emit('event', data) but it fails. Why?

NestJS

import { WebSocketGateway, WebSocketServer } from '@nestjs/websockets';
import { Server } from 'socket.io';

@WebSocketGateway()
export class DebugGateway {
  @WebSocketServer()
  server: Server;

  sendEvent(data: any) {
    this.server.broadcast.emit('event', data);
  }
}

A The server instance requires a namespace before using 'broadcast'.

B 'broadcast' is deprecated and replaced by 'emit' on the server.

C 'broadcast' only works inside client event handlers, not in the gateway class.

D 'broadcast' is not a property of the server instance; it exists on individual sockets.

💡 Hint

Consider where the 'broadcast' property is available in Socket.IO.

The broadcast property exists on socket instances to send to all except the sender. The server instance does not have 'broadcast'.

🧠 Conceptual

expert

How does NestJS handle broadcasting messages in clustered environments?

In a NestJS application running multiple instances behind a load balancer, what must be done to ensure WebSocket broadcasts reach all clients connected to any instance?

A Use a shared adapter like Redis adapter to synchronize broadcasts across instances.

B Broadcasting works automatically across instances without extra setup.

C Use HTTP polling instead of WebSockets to avoid broadcast issues.

D Configure each instance to broadcast only to its own clients; cross-instance broadcast is not possible.

💡 Hint

Think about how multiple server instances share state for WebSocket events.

In clustered setups, a shared adapter like Redis is required to propagate broadcast events to all instances so all clients receive messages.

Practice

1. What does broadcasting messages in a NestJS WebSocket gateway do?

easy

A. Sends a message to only one client

B. Saves messages to a database

C. Sends a message to all connected clients at once

D. Blocks messages from being sent

Solution

1. Step 1: Understand broadcasting meaning

   Broadcasting means sending the same message to everyone connected.

2. Step 2: Apply to NestJS WebSocket gateway

   In NestJS, broadcasting sends messages to all clients, not just one.

3. Final Answer:

   Sends a message to all connected clients at once -> Option C

4. Quick Check:

   Broadcasting = send to all clients [OK]

Hint: Broadcast means send to everyone connected [OK]

Common Mistakes:

• Thinking broadcasting sends to one client only
• Confusing broadcasting with saving messages
• Assuming broadcasting blocks messages

2. Which is the correct way to broadcast a message named 'update' with data in a NestJS WebSocket gateway?

easy

A. this.emit.server('update', data);

B. this.server.emit('update', data);

C. server.this.emit('update', data);

D. emit.this.server('update', data);

Solution

1. Step 1: Recall NestJS WebSocket broadcast syntax

   The correct syntax is calling emit on this.server with event and data.

2. Step 2: Check each option's syntax

   Only this.server.emit('update', data); matches the correct method call: this.server.emit('update', data); others have wrong order or method names.

3. Final Answer:

   this.server.emit('update', data); -> Option B

4. Quick Check:

   Correct emit call = this.server.emit(event, data) [OK]

Hint: Use this.server.emit(event, data) to broadcast [OK]

Common Mistakes:

• Swapping order of 'this' and 'server'
• Using emit as a property instead of a method
• Incorrect method call syntax

3. Given this code inside a NestJS WebSocket gateway:

this.server.emit('notify', { message: 'Hello' });

What will happen when this line runs?

medium

A. The server logs the message but does not send it

B. Only the client who sent the last message receives the event

C. An error occurs because emit needs a callback

D. All connected clients receive the 'notify' event with the message

Solution

1. Step 1: Understand this.server.emit behavior

   This method broadcasts the event to all connected clients.

2. Step 2: Analyze the code effect

   The 'notify' event with the message object is sent to everyone connected.

3. Final Answer:

   All connected clients receive the 'notify' event with the message -> Option D

4. Quick Check:

   this.server.emit sends to all clients [OK]

Hint: Emit on server sends to all clients, not just one [OK]

Common Mistakes:

• Thinking only one client receives the event
• Assuming emit logs instead of sending
• Believing emit requires a callback

4. Identify the error in this NestJS WebSocket gateway code snippet:

this.server.emit('chat', message)

where message is undefined.

medium

A. No error; undefined message is sent as is

B. Runtime error because message must be a string

C. Syntax error due to missing semicolon

D. Emit method requires a callback function

Solution

1. Step 1: Check if undefined data causes error

   Emitting undefined data does not cause syntax or runtime errors in NestJS.

2. Step 2: Confirm emit method requirements

   Emit accepts any data type; no callback is required.

3. Final Answer:

   No error; undefined message is sent as is -> Option A

4. Quick Check:

   Emit accepts undefined data without error [OK]

Hint: Undefined data can be emitted without error [OK]

Common Mistakes:

• Assuming undefined causes runtime error
• Thinking emit needs a callback
• Confusing missing semicolon as error

5. You want to broadcast a message only to clients in a specific room named 'chat-room' in NestJS. Which code correctly does this?

hard

A. this.server.to('chat-room').emit('message', data);

B. this.server.emit('chat-room', 'message', data);

C. this.server.broadcast('chat-room').emit('message', data);

D. this.server.emit('message', data).to('chat-room');

Solution

1. Step 1: Understand broadcasting to rooms in NestJS

   To send to a specific room, use this.server.to(roomName).emit(event, data).

2. Step 2: Check each option for correct syntax

   this.server.to('chat-room').emit('message', data); uses correct chaining: to('chat-room').emit('message', data). Others misuse emit or method order.

3. Final Answer:

   this.server.to('chat-room').emit('message', data); -> Option A

4. Quick Check:

   Broadcast to room = this.server.to(room).emit(event, data) [OK]

Hint: Use this.server.to(room).emit(event, data) for room broadcast [OK]

Common Mistakes:

• Calling emit before to()
• Using broadcast() method which doesn't exist
• Passing room name as event name