Role-based guards in NestJS - Performance & Optimization

Performance: Role-based guards

MEDIUM IMPACT

Role-based guards affect the server response time and user interaction speed by controlling access before executing route handlers.

Controlling access to routes based on user roles

NestJS

import { CanActivate, ExecutionContext, Injectable } from '@nestjs/common';
@Injectable()
export class RoleGuard implements CanActivate {
  canActivate(context: ExecutionContext): boolean {
    const request = context.switchToHttp().getRequest();
    const user = request.user;
    // Simple role check without heavy computation
    return user?.roles?.includes('admin') ?? false;
  }
}

Minimal synchronous checks avoid blocking event loop, allowing faster response and interaction.

📈 Performance GainNon-blocking guard improves INP by reducing server-side delay to under 5 ms.

Controlling access to routes based on user roles

NestJS

import { CanActivate, ExecutionContext, Injectable } from '@nestjs/common';
@Injectable()
export class RoleGuard implements CanActivate {
  canActivate(context: ExecutionContext): boolean {
    const request = context.switchToHttp().getRequest();
    const user = request.user;
    // Check roles inline with complex logic
    if (user && user.roles && user.roles.includes('admin')) {
      // additional heavy synchronous checks
      for (let i = 0; i < 1000000; i++) {}
      return true;
    }
    return false;
  }
}

Heavy synchronous logic inside guard blocks the event loop, delaying response and user interaction.

📉 Performance CostBlocks event loop for 50+ ms per request, increasing INP and server response time.

Performance Comparison

Pattern	Server Processing	Event Loop Blocking	Response Delay	Verdict
Heavy synchronous role checks	High CPU usage	Blocks event loop 50+ ms	Delays response significantly	[X] Bad
Simple role inclusion check	Minimal CPU usage	No event loop blocking	Fast response	[OK] Good

Rendering Pipeline

Role-based guards run before route handlers, affecting server response time which impacts how quickly the browser receives data to render or update UI.

→Server Processing

→Response Time

→User Interaction

⚠️ BottleneckHeavy synchronous logic inside guards blocks the event loop, delaying response.

Core Web Vital Affected

INP

Role-based guards affect the server response time and user interaction speed by controlling access before executing route handlers.

Optimization Tips

1Avoid heavy synchronous logic inside role-based guards to prevent blocking the event loop.

2Keep role checks simple and fast to reduce server response delay.

3Use asynchronous operations carefully to avoid delaying guard completion.

Performance Quiz - 3 Questions

What is the main performance risk of complex synchronous logic inside a NestJS role-based guard?

A It causes layout shifts on the page.

B It increases CSS paint time in the browser.

C It blocks the event loop, delaying server response and user interaction.

D It reduces the bundle size.

DevTools: Performance

How to check: Record a server interaction in DevTools Performance tab, look for long tasks or blocked event loop during guard execution.

What to look for: Long tasks over 50 ms or delayed server response times indicate blocking guard logic.

Practice

1. What is the main purpose of a role-based guard in NestJS?

easy

A. To manage application configuration

B. To handle database connections

C. To format HTTP responses

D. To restrict access to routes based on user roles

Solution

1. Step 1: Understand role-based guard function

   Role-based guards check user roles before allowing access to routes.

2. Step 2: Identify the correct purpose

   Restricting access based on roles matches the guard's role in security.

3. Final Answer:

   To restrict access to routes based on user roles -> Option D

4. Quick Check:

   Role-based guard = restrict access by roles [OK]

Hint: Guards control access; roles limit who can enter [OK]

Common Mistakes:

• Confusing guards with database or config management
• Thinking guards format responses
• Assuming guards handle unrelated tasks

2. Which of the following is the correct way to apply a role-based guard to a route in NestJS?

easy

A. @UseGuards(RolesGuard)\n@Get('profile')

B. @Controller('profile')\n@RolesGuard()

C. @Roles('admin')\n@UseGuards(AuthGuard)

D. @UseGuards(AuthGuard)\n@Get('profile')

Solution

1. Step 1: Identify correct guard usage syntax

   Use @UseGuards with the guard class to apply it to routes.

2. Step 2: Match with role-based guard usage

   @UseGuards(RolesGuard) is correct; @Roles decorator marks roles separately.

3. Final Answer:

   @UseGuards(RolesGuard)\n@Get('profile') -> Option A

4. Quick Check:

   @UseGuards(RolesGuard) applies guard [OK]

Hint: Use @UseGuards with guard class to protect routes [OK]

Common Mistakes:

• Using @RolesGuard() instead of @UseGuards
• Mixing @Roles and @UseGuards incorrectly
• Applying guards without @UseGuards decorator

3. Given this guard code snippet, what will be the result if the user role is 'user' and the route requires 'admin' role?

canActivate(context: ExecutionContext) {
  const roles = this.reflector.get('roles', context.getHandler());
  const request = context.switchToHttp().getRequest();
  const user = request.user;
  return roles.includes(user.role);
}

medium

A. Access granted

B. Access denied

C. Runtime error due to missing roles

D. Always returns true

Solution

1. Step 1: Understand role check logic

   The guard checks if the user's role is included in the allowed roles array.

2. Step 2: Apply given roles and user role

   User role is 'user', route requires 'admin', so roles.includes('user') is false.

3. Final Answer:

   Access denied -> Option B

4. Quick Check:

   User role not in allowed roles = deny access [OK]

Hint: Check if user role is in allowed roles array [OK]

Common Mistakes:

• Assuming access is granted if roles differ
• Thinking roles includes user role always
• Ignoring roles array presence

4. Identify the error in this role-based guard implementation:

canActivate(context: ExecutionContext) {
  const roles = this.reflector.get('roles', context.getHandler());
  const request = context.switchToHttp().getRequest();
  const user = request.user;
  if (!roles) {
    return false;
  }
  return roles.includes(user.role);
}

medium

A. Returns false if no roles metadata, blocking all access

B. Missing async keyword causes runtime error

C. Incorrect use of context.getHandler()

D. Should check user permissions instead of roles

Solution

1. Step 1: Analyze roles metadata check

   If roles metadata is missing, the guard returns false blocking access.

2. Step 2: Understand typical behavior for missing roles

   Usually, missing roles means no restriction, so returning false is too strict.

3. Final Answer:

   Returns false if no roles metadata, blocking all access -> Option A

4. Quick Check:

   No roles metadata should allow access, not block [OK]

Hint: Missing roles metadata should not block access by default [OK]

Common Mistakes:

• Assuming missing roles means deny access
• Forgetting to handle undefined roles gracefully
• Confusing async necessity in this context

5. You want to create a role-based guard that allows access if the user has any one of multiple roles specified on a route. Which approach correctly implements this behavior?

hard

A. Use multiple guards each checking one role and combine them with @UseGuards

B. Check only the first role in roles array against user.role in canActivate

C. Use @Roles('admin', 'editor') decorator and check if user.role is included in roles array inside canActivate

D. Ignore roles and allow access to all authenticated users

Solution

1. Step 1: Understand multiple roles in @Roles decorator

   @Roles can accept multiple roles as arguments to specify allowed roles.

2. Step 2: Implement canActivate to check inclusion

   Checking if user.role is in roles array allows access if user has any allowed role.

3. Final Answer:

   Use @Roles('admin', 'editor') decorator and check if user.role is included in roles array inside canActivate -> Option C

4. Quick Check:

   Check user role in roles array for multiple allowed roles [OK]

Hint: Check if user role is in roles array for multiple roles [OK]

Common Mistakes:

• Checking only first role ignores others
• Using multiple guards unnecessarily
• Allowing all authenticated users ignores roles