Why Cache interceptor in NestJS? - Purpose & Use Cases

The Big Idea

What if your server could remember answers and save time without you lifting a finger?

The Scenario

Imagine your server has to process the same request multiple times, like fetching user data every time someone clicks a button.

Each time, it repeats the same heavy work, slowing down responses and wasting resources.

The Problem

Manually handling caching means writing extra code everywhere.

This is error-prone, easy to forget, and hard to maintain.

It also clutters your business logic and can cause inconsistent data if not done carefully.

The Solution

The Cache interceptor in NestJS automatically stores and returns cached responses for repeated requests.

This keeps your code clean and speeds up responses without extra manual work.

Before vs After

✗ Before

if (cache.has(key)) {
  return cache.get(key);
}
const result = await fetchData();
cache.set(key, result);
return result;

✓ After

@UseInterceptors(CacheInterceptor)
async getData() {
  return await fetchData();
}

What It Enables

It enables fast, efficient responses by reusing previous results automatically, improving user experience and saving server power.

Real Life Example

Think of an online store showing product details. Instead of fetching the same product info from the database every time, the Cache interceptor quickly serves the stored data.

Key Takeaways

Manual caching is repetitive and error-prone.

Cache interceptor automates caching cleanly and reliably.

This leads to faster responses and simpler code.

Practice

1. What is the main purpose of the CacheInterceptor in NestJS?

easy

A. To handle authentication and authorization

B. To store responses and speed up repeated requests

C. To log all incoming requests

D. To format response data before sending

Solution

1. Step 1: Understand the role of CacheInterceptor

   The CacheInterceptor caches HTTP responses to avoid recomputing them on repeated requests.

2. Step 2: Compare with other options

   Logging, authentication, and formatting are handled by other interceptors or middleware, not CacheInterceptor.

3. Final Answer:

   To store responses and speed up repeated requests -> Option B

4. Quick Check:

   CacheInterceptor caches responses = C [OK]

Hint: CacheInterceptor caches responses to speed up requests [OK]

Common Mistakes:

• Confusing CacheInterceptor with logging interceptors
• Thinking it handles security tasks
• Assuming it formats data

2. Which of the following is the correct way to apply the CacheInterceptor to a controller method in NestJS?

easy

A. Add CacheInterceptor in the constructor of the controller

B. @Cacheable() decorator on the method

C. @UseInterceptors(CacheInterceptor) above the method

D. Use @CacheInterceptor() as a method parameter

Solution

1. Step 1: Recall how to apply interceptors in NestJS

   Interceptors are applied using the @UseInterceptors() decorator above methods or controllers.

2. Step 2: Check each option

   Only @UseInterceptors(CacheInterceptor) above the method uses the correct decorator syntax. Options B, C, and D are invalid or do not exist in NestJS.

3. Final Answer:

   @UseInterceptors(CacheInterceptor) above the method -> Option C

4. Quick Check:

   UseInterceptors decorator = A [OK]

Hint: Use @UseInterceptors(CacheInterceptor) to apply caching [OK]

Common Mistakes:

• Using non-existent @Cacheable decorator
• Trying to inject interceptor in constructor
• Passing interceptor as method parameter

3. Given this code snippet, what will be the output on the second request to /hello?

import { Controller, Get, UseInterceptors } from '@nestjs/common';
import { CacheInterceptor } from '@nestjs/cache-manager';

@Controller()
export class HelloController {
  private count = 0;

  @UseInterceptors(CacheInterceptor)
  @Get('hello')
  getHello() {
    this.count++;
    return `Hello count: ${this.count}`;
  }
}

medium

A. "Hello count: 1" first request, "Hello count: 2" second request

B. Error because count is private

C. "Hello count: 0" on both requests

D. "Hello count: 1" on first and second request

Solution

1. Step 1: Understand CacheInterceptor behavior

   CacheInterceptor caches the response of the first request and returns it for subsequent requests without calling the method again.

2. Step 2: Analyze the count variable increment

   On the first request, count increments to 1 and returns "Hello count: 1". On the second request, the cached response is returned, so count does not increment again.

3. Final Answer:

   "Hello count: 1" on first and second request -> Option D

4. Quick Check:

   Cache returns cached response = B [OK]

Hint: CacheInterceptor returns cached response, method not re-executed [OK]

Common Mistakes:

• Assuming count increments on every request
• Thinking private variables cause errors here
• Ignoring caching effect on method execution

4. Identify the error in this NestJS CacheInterceptor usage:

import { Controller, Get, UseInterceptors } from '@nestjs/common';
import { CacheInterceptor } from '@nestjs/cache-manager';

@Controller()
export class TestController {
  @UseInterceptors(CacheInterceptor())
  @Get('test')
  test() {
    return 'Test response';
  }
}

medium

A. CacheInterceptor should not be called as a function

B. Missing CacheModule import in the controller

C. Method test must be async to use CacheInterceptor

D. CacheInterceptor must be applied globally, not per method

Solution

1. Step 1: Check how CacheInterceptor is applied

   CacheInterceptor is a class, not a function, so it should be passed without parentheses to @UseInterceptors().

2. Step 2: Verify other options

   CacheModule import is required but not shown here (not an error in this snippet). Method does not need to be async. CacheInterceptor can be applied per method.

3. Final Answer:

   CacheInterceptor should not be called as a function -> Option A

4. Quick Check:

   Use class name without () = A [OK]

Hint: Pass CacheInterceptor class, not call it as function [OK]

Common Mistakes:

• Calling CacheInterceptor with parentheses
• Assuming method must be async
• Thinking CacheModule import error here

5. You want to customize the cache key for a route in NestJS using CacheInterceptor. Which approach correctly achieves this?

hard

A. Extend CacheInterceptor and override the trackBy method to return a custom key

B. Pass a custom key string directly to @UseInterceptors(CacheInterceptor)

C. Set a custom key in the controller constructor

D. Use @CacheKey('customKey') decorator on the method

Solution

1. Step 1: Understand how to customize cache keys

   CacheInterceptor allows customization by extending it and overriding the trackBy method to define how keys are generated.

2. Step 2: Evaluate other options

   Passing a string to @UseInterceptors() is invalid. Setting keys in constructor or using @CacheKey decorator does not exist in NestJS.

3. Final Answer:

   Extend CacheInterceptor and override the trackBy method to return a custom key -> Option A

4. Quick Check:

   Override trackBy method = D [OK]

Hint: Override trackBy method in extended CacheInterceptor [OK]

Common Mistakes:

• Trying to pass key directly to decorator
• Using non-existent @CacheKey decorator
• Setting keys in constructor instead of method