Route handlers (GET, POST, PUT, DELETE) in NestJS - Performance & Optimization

Performance: Route handlers (GET, POST, PUT, DELETE)

MEDIUM IMPACT

This affects server response time and client perceived latency by how efficiently route handlers process requests and send responses.

Handling HTTP requests with route handlers in NestJS

NestJS

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

@Controller('items')
export class ItemsController {
  @Get()
  async getAll() {
    // Asynchronous non-blocking operation
    const data = await this.fetchItemsFromDb();
    return { data };
  }

  async fetchItemsFromDb() {
    // Simulate async DB call
    return new Promise(resolve => setTimeout(() => resolve(['item1', 'item2']), 50));
  }
}

Using async/await avoids blocking the event loop, allowing other requests to be processed concurrently.

📈 Performance GainNon-blocking, reduces server response delay, improves INP metric.

Handling HTTP requests with route handlers in NestJS

NestJS

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

@Controller('items')
export class ItemsController {
  @Get()
  getAll() {
    // Synchronous heavy computation or blocking code
    for (let i = 0; i < 1e9; i++) {}
    return { data: 'All items' };
  }
}

Blocking synchronous code delays response, causing slow server replies and poor user experience.

📉 Performance CostBlocks event loop, increasing response time by hundreds of milliseconds or more.

Performance Comparison

Pattern	Server Processing	Event Loop Blocking	Response Time	Verdict
Synchronous blocking handlers	High CPU usage	Blocks event loop	Slow responses	[X] Bad
Asynchronous non-blocking handlers	Efficient CPU usage	No blocking	Fast responses	[OK] Good

Rendering Pipeline

Route handlers process incoming HTTP requests on the server, affecting how quickly responses are generated and sent back to the client. Slow or blocking handlers delay response generation, increasing interaction latency.

→Server Processing

→Network Response

→Client Rendering

⚠️ BottleneckServer Processing (event loop blocking or heavy synchronous work)

Core Web Vital Affected

INP

This affects server response time and client perceived latency by how efficiently route handlers process requests and send responses.

Optimization Tips

1Avoid synchronous blocking code in route handlers to keep the event loop free.

2Use async/await and non-blocking calls for database or heavy operations.

3Monitor server response times to detect slow route handlers affecting user experience.

Performance Quiz - 3 Questions

What is the main performance problem with synchronous blocking code in NestJS route handlers?

A It causes layout shifts in the browser

B It increases bundle size significantly

C It blocks the event loop, delaying all other requests

D It improves server throughput

DevTools: Network and Performance panels

How to check: Use Network panel to measure response times of API calls. Use Performance panel to record server response delays and event loop blocking.

What to look for: Look for long server response times and event loop blocking indicators that show slow route handler execution.