Guard binding levels in NestJS - Performance & Optimization

Performance: Guard binding levels

MEDIUM IMPACT

This affects the request processing speed and server response time by controlling how often guards run during request handling.

Applying guards to control access in a NestJS application

NestJS

import { Injectable, CanActivate, ExecutionContext, Controller, UseGuards } from '@nestjs/common';

@Injectable()
export class AuthGuard implements CanActivate {
  canActivate(context: ExecutionContext): boolean {
    // auth logic
    return true;
  }
}

// Binding guard only on specific controllers or routes
@Controller('users')
@UseGuards(AuthGuard)
export class UsersController {}

The guard runs only on routes that require it, reducing unnecessary checks and improving request throughput.

📈 Performance GainGuard executes only on targeted routes, reducing CPU load and improving average response time.

Applying guards to control access in a NestJS application

NestJS

import { Injectable, CanActivate, ExecutionContext } from '@nestjs/common';

@Injectable()
export class AuthGuard implements CanActivate {
  canActivate(context: ExecutionContext): boolean {
    // heavy auth logic
    return true;
  }
}

// Binding guard globally in main.ts
app.useGlobalGuards(new AuthGuard());

The guard runs on every request, even for routes that don't need authentication, causing unnecessary processing.

📉 Performance CostTriggers guard execution for 100% of requests, increasing server CPU usage and response time.

Performance Comparison

Pattern	Guard Executions	CPU Usage	Response Delay	Verdict
Global guard binding	Runs on all requests	High	Increased latency	[X] Bad
Controller-level guard binding	Runs on specific controllers	Medium	Moderate latency	[!] OK
Method-level guard binding	Runs only on specific routes	Low	Minimal latency	[OK] Good

Rendering Pipeline

In NestJS, guard binding levels determine when guard logic runs during the request lifecycle, affecting server-side processing before response generation.

→Request Handling

→Middleware Execution

→Route Handler Invocation

⚠️ BottleneckExcessive guard executions on unrelated routes increase CPU usage and delay response generation.

Optimization Tips

1Bind guards only where necessary to avoid unnecessary processing.

2Avoid global guards if many routes do not require them.

3Use method-level guards for fine-grained control and better performance.

Performance Quiz - 3 Questions

What is the main performance drawback of binding a guard globally in NestJS?

A The guard cannot access request data.

B The guard runs on every request, even when not needed.

C The guard causes client-side rendering delays.

D The guard increases bundle size significantly.

DevTools: Network and Performance panels

How to check: Use Network panel to measure response times for guarded vs unguarded routes. Use Performance panel to profile CPU usage during request handling.

What to look for: Look for increased server response times and CPU spikes on routes with global guards compared to scoped guards.

Practice

1. Which of the following is true about guard binding levels in NestJS?

easy

A. Route guards apply to all controllers automatically.

B. Global guards apply to all routes in the application.

C. Controller guards cannot be overridden by route guards.

D. Guards can only be applied globally, not to specific routes.

Solution

1. Step 1: Understand global guard scope

   Global guards are set once and protect every request in the app.

2. Step 2: Compare with other guard levels

   Route guards apply only to specific routes, and controller guards apply to all routes in a controller. Route guards can override controller guards.

3. Final Answer:

   Global guards apply to all routes in the application. -> Option B

4. Quick Check:

   Global guard = all routes [OK]

Hint: Global guards protect all routes, no exceptions [OK]

Common Mistakes:

• Thinking route guards apply globally
• Believing controller guards cannot be overridden
• Assuming guards can't be applied to routes

2. Which is the correct way to bind a guard to a specific route in NestJS?

easy

A. Use @GlobalGuard decorator on the route

B. @UseGuards(MyGuard) above the controller class

C. Add MyGuard to the global providers array

D. @UseGuards(MyGuard) above the route handler method

Solution

1. Step 1: Identify route-level guard binding

   To bind a guard to a specific route, place @UseGuards() decorator above the route handler method.

2. Step 2: Differentiate from other bindings

   @UseGuards() above the controller binds to all routes in that controller. Global guards are set differently, and @GlobalGuard does not exist.

3. Final Answer:

   @UseGuards(MyGuard) above the route handler method -> Option D

4. Quick Check:

   Route guard = @UseGuards on method [OK]

Hint: Use @UseGuards on method for route-level guards [OK]

Common Mistakes:

• Putting @UseGuards only on controller for route guard
• Confusing global providers with route guards
• Using non-existent @GlobalGuard decorator

3. Given this code snippet, what will happen when a request hits the GET /users/profile route?

@UseGuards(GlobalGuard)
@Controller('users')
@UseGuards(ControllerGuard)
export class UserController {
  @Get('profile')
  @UseGuards(RouteGuard)
  getProfile() {
    return 'User Profile';
  }
}

medium

A. GlobalGuard, ControllerGuard, and RouteGuard all run in order.

B. Only GlobalGuard runs before the route handler.

C. Only RouteGuard runs, ignoring others.

D. ControllerGuard overrides and disables other guards.

Solution

1. Step 1: Identify guard binding levels in code

   GlobalGuard is bound globally, ControllerGuard on the controller, and RouteGuard on the route method.

2. Step 2: Understand guard execution order

   All guards bound at different levels run in order: global first, then controller, then route.

3. Final Answer:

   GlobalGuard, ControllerGuard, and RouteGuard all run in order. -> Option A

4. Quick Check:

   All guards run in binding order [OK]

Hint: All guards at different levels run in sequence [OK]

Common Mistakes:

• Assuming only one guard runs
• Thinking controller guard disables others
• Believing global guard runs alone

4. You have a guard bound globally and another bound to a controller. The controller guard is not running on requests. What is the likely cause?

medium

A. The controller guard was not added to the controller with @UseGuards.

B. Controller guards cannot be used with global guards.

C. Guards must be bound only at one level, not multiple.

D. The global guard is blocking all requests before the controller guard runs.

Solution

1. Step 1: Check guard binding syntax

   Controller guards must be explicitly added with @UseGuards on the controller class.

2. Step 2: Understand guard coexistence

   Global and controller guards can coexist; global guards do not block controller guards from running.

3. Final Answer:

   The controller guard was not added to the controller with @UseGuards. -> Option A

4. Quick Check:

   Missing @UseGuards on controller = no controller guard [OK]

Hint: Always add @UseGuards to controller for controller guards [OK]

Common Mistakes:

• Thinking global guard blocks controller guards
• Believing guards can't be combined
• Forgetting to decorate controller with @UseGuards

5. You want to apply a guard that blocks access to all routes except one specific route in a controller. Which approach correctly uses guard binding levels to achieve this?

hard

A. Bind the guard globally and use a route-level guard to allow the exception route.

B. Bind the guard only on the exception route to block all others.

C. Bind the guard on the controller and override it with a route-level guard that allows the exception.

D. Bind the guard globally and remove it from the exception route using @SkipGuards.

Solution

1. Step 1: Understand guard override behavior

   Controller-level guards apply to all routes in that controller but can be overridden by route-level guards.

2. Step 2: Apply guard to block all except one route

   Binding the guard on the controller blocks all routes; then a route-level guard on the exception route can allow access.

3. Final Answer:

   Bind the guard on the controller and override it with a route-level guard that allows the exception. -> Option C

4. Quick Check:

   Controller guard + route override = selective access [OK]

Hint: Use controller guard plus route guard override for exceptions [OK]

Common Mistakes:

• Trying to remove global guards per route (not supported)
• Binding guard only on exception route (wrong logic)
• Assuming global guard can be skipped per route