Why authentication secures NestJS APIs - Performance Evidence

Performance: Why authentication secures NestJS APIs

MEDIUM IMPACT

Authentication affects API request handling speed and server response time by adding verification steps before processing requests.

Protecting API endpoints from unauthorized access

NestJS

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

@Injectable()
export class AuthGuard implements CanActivate {
  constructor(private jwtService: JwtService) {}

  async canActivate(context: ExecutionContext): Promise<boolean> {
    const request = context.switchToHttp().getRequest();
    const token = request.headers['authorization'];
    if (!token) return false;
    try {
      const user = await this.jwtService.verifyAsync(token);
      request.user = user;
      return true;
    } catch {
      return false;
    }
  }
}

Asynchronous token verification avoids blocking, allowing other requests to be processed concurrently.

📈 Performance GainNon-blocking verification improves INP and overall API responsiveness.

Protecting API endpoints from unauthorized access

NestJS

app.use((req, res, next) => {
  const token = req.headers['authorization'];
  if (!token) {
    res.status(401).send('Unauthorized');
  } else {
    // Synchronous token verification blocking event loop
    const user = verifyTokenSync(token);
    if (!user) {
      res.status(401).send('Unauthorized');
    } else {
      req.user = user;
      next();
    }
  }
});

Synchronous token verification blocks the event loop, delaying all incoming requests.

📉 Performance CostBlocks event loop for each request, increasing INP and slowing response times.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous token verification	N/A	N/A	N/A	[X] Bad
Asynchronous token verification with JwtService	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

Authentication runs before request handlers, adding a verification step that affects server response timing but not browser rendering directly.

→Request Handling

→Server Processing

⚠️ BottleneckSynchronous token verification blocking the event loop

Core Web Vital Affected

INP

Authentication affects API request handling speed and server response time by adding verification steps before processing requests.

Optimization Tips

1Avoid synchronous token verification to prevent blocking the event loop.

2Use asynchronous methods like JwtService.verifyAsync for token validation.

3Cache authentication results when possible to reduce repeated work.

Performance Quiz - 3 Questions

What is the main performance risk of synchronous authentication in NestJS APIs?

A It increases CSS paint time

B It blocks the event loop, delaying all requests

C It causes layout shifts in the browser

D It increases bundle size significantly

DevTools: Performance

How to check: Record a server profile while making authenticated API requests; look for long blocking tasks or event loop delays.

What to look for: Long blocking tasks indicate synchronous operations slowing response; short, async tasks indicate good performance.

Practice

1. Why is authentication important for securing NestJS APIs?

easy

A. It stops strangers from accessing protected routes.

B. It speeds up the API response time.

C. It automatically fixes bugs in the code.

D. It changes the API's data format.

Solution

1. Step 1: Understand the purpose of authentication

   Authentication verifies who is using the API to prevent unauthorized access.

2. Step 2: Identify the effect on API security

   By stopping strangers, authentication protects sensitive data and functionality.

3. Final Answer:

   It stops strangers from accessing protected routes. -> Option A

4. Quick Check:

   Authentication = Stops strangers [OK]

Hint: Authentication blocks unknown users from API access [OK]

Common Mistakes:

• Thinking authentication speeds up API
• Believing it fixes code bugs
• Confusing authentication with data formatting

2. Which of the following is the correct way to apply an authentication guard in a NestJS controller?

easy

A. @AuthGuard('jwt') export class MyController {}

B. @UseGuards(AuthGuard('jwt')) export class MyController {}

C. @UseAuthGuard('jwt') export class MyController {}

D. @GuardUse(Auth('jwt')) export class MyController {}

Solution

1. Step 1: Recall NestJS guard syntax

   Guards are applied using the @UseGuards() decorator with the guard class or strategy inside.

2. Step 2: Match the correct syntax for JWT guard

   The correct syntax is @UseGuards(AuthGuard('jwt')) to apply the JWT strategy.

3. Final Answer:

   @UseGuards(AuthGuard('jwt')) export class MyController {} -> Option B

4. Quick Check:

   @UseGuards(AuthGuard('jwt')) = Correct syntax [OK]

Hint: Use @UseGuards with AuthGuard('jwt') for authentication [OK]

Common Mistakes:

• Using wrong decorator names like @AuthGuard
• Swapping order of decorator and parameters
• Misspelling @UseGuards

3. Given this NestJS controller snippet, what happens when a request without a valid JWT token is sent?

@UseGuards(AuthGuard('jwt'))
@Get('profile')
getProfile() {
  return { message: 'Access granted' };
}

medium

A. The request is denied with a 401 Unauthorized error.

B. The request returns an empty response.

C. The request causes a server crash.

D. The request is allowed and returns { message: 'Access granted' }.

Solution

1. Step 1: Understand AuthGuard('jwt') behavior

   This guard checks for a valid JWT token and blocks requests without it.

2. Step 2: Predict response for missing or invalid token

   Without a valid token, the guard denies access and returns a 401 Unauthorized error.

3. Final Answer:

   The request is denied with a 401 Unauthorized error. -> Option A

4. Quick Check:

   Invalid token = 401 error [OK]

Hint: No valid JWT means 401 Unauthorized response [OK]

Common Mistakes:

• Assuming request passes without token
• Expecting server crash on missing token
• Thinking empty response is returned

4. Identify the error in this NestJS authentication guard usage:

@UseGuards(AuthGuard)
@Get('data')
getData() {
  return { data: 'secret' };
}

medium

A. The @UseGuards decorator is misspelled.

B. The getData method should be async.

C. AuthGuard is missing the strategy name like 'jwt'.

D. The route path 'data' is invalid.

Solution

1. Step 1: Check AuthGuard usage

   AuthGuard requires a strategy name like 'jwt' to know which authentication method to use.

2. Step 2: Identify missing strategy parameter

   Here, AuthGuard is used without ('jwt'), causing it to not work properly.

3. Final Answer:

   AuthGuard is missing the strategy name like 'jwt'. -> Option C

4. Quick Check:

   AuthGuard needs strategy name [OK]

Hint: Always provide strategy name to AuthGuard like 'jwt' [OK]

Common Mistakes:

• Forgetting to add strategy name to AuthGuard
• Thinking method must be async
• Assuming route path 'data' is invalid

5. You want to secure a NestJS API route so only logged-in users can access it. Which combination correctly applies authentication and explains why it secures the API? Options: A) Use @UseGuards(AuthGuard('jwt')) to check user identity before route access, preventing strangers. B) Use @UseInterceptors(AuthInterceptor) to log requests, which blocks unauthorized users. C) Use @UseFilters(AuthFilter) to catch errors, which stops unauthorized access. D) Use @UsePipes(AuthPipe) to validate data, which ensures only valid users access the route.

hard

A. Use @UsePipes(AuthPipe) to validate data, which ensures only valid users access the route.

B. Use @UseInterceptors(AuthInterceptor) to log requests, which blocks unauthorized users.

C. Use @UseFilters(AuthFilter) to catch errors, which stops unauthorized access.

D. Use @UseGuards(AuthGuard('jwt')) to check user identity before route access, preventing strangers.

Solution

1. Step 1: Identify the correct NestJS feature for authentication

   Guards are designed to control access by checking user identity before route execution.

2. Step 2: Understand why guards secure APIs

   Using @UseGuards(AuthGuard('jwt')) ensures only authenticated users with valid JWT tokens can access the route, blocking strangers.

3. Final Answer:

   Use @UseGuards(AuthGuard('jwt')) to check user identity before route access, preventing strangers. -> Option D

4. Quick Check:

   Guards + AuthGuard('jwt') = Secure API access [OK]

Hint: Use guards with AuthGuard('jwt') to secure routes [OK]

Common Mistakes:

• Confusing interceptors, filters, or pipes with authentication guards
• Thinking logging or error handling blocks unauthorized users
• Assuming data validation equals authentication