Why WebSockets enable real-time features in NestJS - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How do WebSockets maintain a continuous connection?

In NestJS, WebSockets allow a server and client to communicate continuously. How does this connection stay open?

A WebSockets create a single TCP connection that stays open for ongoing two-way communication.

B The client sends a new HTTP request for every message to keep the connection alive.

C The server repeatedly closes and reopens connections to simulate real-time updates.

D WebSockets use multiple short-lived HTTP requests to mimic a continuous connection.

💡 Hint

Think about how a phone call stays open versus sending letters back and forth.

WebSockets establish a single TCP connection that remains open, allowing instant two-way communication without repeated handshakes.

❓ component_behavior

intermediate

What happens when a NestJS WebSocket Gateway receives a message?

Consider a NestJS WebSocket Gateway that listens for messages. What is the typical behavior when a message arrives?

NestJS

import { WebSocketGateway, SubscribeMessage, MessageBody } from '@nestjs/websockets';

@WebSocketGateway()
export class ChatGateway {
  @SubscribeMessage('message')
  handleMessage(@MessageBody() data: string): string {
    return `Received: ${data}`;
  }
}

A The server processes the message and sends a response back to the client immediately.

B The server queues the message but does not send any response.

C The server ignores the message and waits for the next one.

D The server closes the connection after receiving the message.

💡 Hint

Think about how a chat app replies instantly when you send a message.

The Gateway listens for specific events, processes incoming messages, and can send immediate responses back to the client over the open WebSocket connection.

❓ lifecycle

advanced

What lifecycle event occurs when a client disconnects from a NestJS WebSocket Gateway?

In NestJS WebSocket Gateway, which lifecycle method is triggered when a client disconnects?

NestJS

import { WebSocketGateway, OnGatewayDisconnect } from '@nestjs/websockets';

@WebSocketGateway()
export class ChatGateway implements OnGatewayDisconnect {
  handleDisconnect(client: any) {
    console.log('Client disconnected');
  }
}

A handleConnection()

B handleDisconnect()

C afterInit()

D handleMessage()

💡 Hint

Think about the name that suggests a client leaving or disconnecting.

The handleDisconnect() method is called automatically when a client disconnects from the WebSocket Gateway.

📝 Syntax

advanced

Which code snippet correctly broadcasts a message to all connected clients in NestJS WebSocket Gateway?

Choose the correct way to send a message to all clients connected to a NestJS WebSocket Gateway.

NestJS

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

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

  broadcastMessage(message: string) {
    // Fill in the blank
  }
}

A this.server.sendMessage('message', message);

B this.server.send('message', message);

C this.server.emit('message', message);

D this.server.broadcast('message', message);

💡 Hint

Look for the method that sends an event to all clients in Socket.IO.

The emit method sends an event with data to all connected clients in Socket.IO, which NestJS uses under the hood.

🔧 Debug

expert

Why does this NestJS WebSocket Gateway fail to receive messages?

Given the following code, why does the server never log incoming messages?

NestJS

import { WebSocketGateway, SubscribeMessage, MessageBody } from '@nestjs/websockets';

@WebSocketGateway()
export class ChatGateway {
  @SubscribeMessage('chat')
  handleChat(@MessageBody() data: string) {
    console.log('Message:', data);
  }
}

A The handleChat method must return a value to receive messages.

B The @SubscribeMessage decorator is missing a required second argument.

C The WebSocketGateway decorator requires a port number to work.

D The client is sending messages with event name 'message' instead of 'chat'.

💡 Hint

Check if the event names between client and server match exactly.

The server listens for 'chat' events, but if the client sends 'message' events, the handler won't trigger.