Why controllers handle incoming requests in NestJS - Visual Breakdown

Concept Flow - Why controllers handle incoming requests

Client sends HTTP request

↓

NestJS Router receives request

↓

Controller matches route

↓

Controller method executes

↓

Controller processes data

↓

Controller returns response

↓

Response sent back to client

This flow shows how a controller in NestJS receives an HTTP request, processes it, and sends back a response.

Execution Sample

NestJS

import { Controller, Get } from '@nestjs/common';

@Controller('hello')
export class HelloController {
  @Get()
  sayHello() {
    return 'Hello World!';
  }
}

A simple controller that handles GET requests to '/hello' and returns a greeting.

Execution Table

Step	Action	Input	Controller Method	Output
1	Client sends GET request to /hello	/hello	N/A	Request received by NestJS router
2	Router matches route to HelloController	/hello	N/A	Route matched to HelloController.sayHello()
3	Controller method sayHello() executes	N/A	sayHello()	Returns 'Hello World!'
4	NestJS sends response back to client	N/A	N/A	Response: 'Hello World!'

💡 Request handled and response sent, flow ends.

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
requestUrl	undefined	/hello	/hello	/hello
matchedController	undefined	HelloController	HelloController	HelloController
responseData	undefined	undefined	'Hello World!'	'Hello World!'

Key Moments - 2 Insights

Why does the controller method run only after the router matches the route?

Because the router first checks the URL to find the right controller. Only then does it call the controller method, as shown in execution_table step 2 and 3.

What happens if no controller matches the incoming request?

The router cannot find a matching controller, so the request is not handled and usually a 404 error is returned. This is before step 3 in the execution_table.

Visual Quiz - 3 Questions

Look at the execution table, what is the output after step 3?

A Request received by NestJS router

B 'Hello World!'

C Route matched to HelloController.sayHello()

D Response sent back to client

💡 Hint

Check the 'Output' column in row for step 3.

At which step does the router match the incoming request to the controller?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Action' column describing route matching.

If the controller method returned a different string, how would the variable 'responseData' change?

A It would change to the new returned string

B It would stay 'Hello World!'

C It would become undefined

D It would cause an error

💡 Hint

See variable_tracker 'responseData' changes after step 3.

Concept Snapshot

Controllers in NestJS handle incoming HTTP requests.
They match routes to methods that process requests.
Controllers return responses sent back to clients.
The router directs requests to the right controller.
This keeps request handling organized and clear.

Full Transcript

In NestJS, when a client sends an HTTP request, the NestJS router receives it first. The router checks the URL and matches it to a controller based on the route. Once matched, the controller method runs to process the request. The controller returns data, which NestJS sends back as the response. This flow ensures that each request is handled by the correct part of the application, keeping things organized and easy to manage.