Caching

Caching is a great and simple technique that helps improve your app’s performance. It acts as a temporary data store providing high performance data access.

Installation

First install the required package:

  2. $ npm install --save cache-manager

In-memory cache

Nest provides a unified API for various cache storage providers. The built-in one is an in-memory data store. However, you can easily switch to a more comprehensive solution, like Redis. In order to enable caching, first import the CacheModule and call its register() method.

  2. import { CacheModule, Module } from '@nestjs/common';
  3. import { AppController } from './app.controller';
  5. @Module({
  6.   imports: [CacheModule.register()],
  7.   controllers: [AppController],
  8. })
  9. export class ApplicationModule {}

Warning In GraphQL applications, interceptors are executed separately for each field resolver. Thus, CacheModule (which uses interceptors to cache responses) will not work properly.

Then just tie the CacheInterceptor where you want to cache data.

  2. @Controller()
  3. @UseInterceptors(CacheInterceptor)
  4. export class AppController {
  5.   @Get()
  6.   findAll(): string[] {
  7.     return [];
  8.   }
  9. }

Warning Only GET endpoints are cached. Also, HTTP server routes that inject the native response object (@Res()) cannot use the Cache Interceptor. See response mapping for more details.

Global cache

To reduce the amount of required boilerplate, you can bind CacheInterceptor to all endpoints globally:

  2. import { CacheModule, Module, CacheInterceptor } from '@nestjs/common';
  3. import { AppController } from './app.controller';
  4. import { APP_INTERCEPTOR } from '@nestjs/core';
  6. @Module({
  7.   imports: [CacheModule.register()],
  8.   controllers: [AppController],
  9.   providers: [
  10.     {
  11.       provide: APP_INTERCEPTOR,
  12.       useClass: CacheInterceptor,
  13.     },
  14.   ],
  15. })
  16. export class ApplicationModule {}

Customize caching

All cached data has its own expiration time (TTL). To customize default values, pass the options object to the register() method.

  2. CacheModule.register({
  3.   ttl: 5, // seconds
  4.   max: 10, // maximum number of items in cache
  5. });

Global cache overrides

While global cache is enabled, cache entries are stored under a CacheKey that is auto-generated based on the route path. You may override certain cache settings (@CacheKey() and @CacheTTL()) on a per-method basis, allowing customized caching strategies for individual controller methods. This may be most relevant while using different cache stores.

  2. @Controller()
  3. export class AppController {
  4.   @CacheKey('custom_key')
  5.   @CacheTTL(20)
  6.   findAll(): string[] {
  7.     return [];
  8.   }
  9. }

Hint The @CacheKey() and @CacheTTL() decorators are imported from the @nestjs/common package.

The @CacheKey() decorator may be used with or without a corresponding @CacheTTL() decorator and vice versa. One may choose to override only the @CacheKey() or only the @CacheTTL(). Settings that are not overridden with a decorator will use the default values as registered globally (see Customize caching).

WebSockets and Microservices

You can also apply the CacheInterceptor to WebSocket subscribers as well as Microservice’s patterns (regardless of the transport method that is being used).

  2. @CacheKey('events')
  3. @UseInterceptors(CacheInterceptor)
  4. @SubscribeMessage('events')
  5. handleEvent(client: Client, data: string[]): Observable<string[]> {
  6.   return [];
  7. }
  2. @CacheKey('events')
  3. @UseInterceptors(CacheInterceptor)
  4. @SubscribeMessage('events')
  5. handleEvent(client, data) {
  6.   return [];
  7. }

However, the additional @CacheKey() decorator is required in order to specify a key used to subsequently store and retrieve cached data. Also, please note that you shouldn’t cache everything. Actions which perform some business operations rather than simply querying the data should never be cached.

Additionally, you may specify a cache expiration time (TTL) by using the @CacheTTL() decorator, which will override the global default TTL value.

  2. @CacheTTL(10)
  3. @UseInterceptors(CacheInterceptor)
  4. @SubscribeMessage('events')
  5. handleEvent(client: Client, data: string[]): Observable<string[]> {
  6.   return [];
  7. }
  2. @CacheTTL(10)
  3. @UseInterceptors(CacheInterceptor)
  4. @SubscribeMessage('events')
  5. handleEvent(client, data) {
  6.   return [];
  7. }

Hint The @CacheTTL() decorator may be used with or without a corresponding @CacheKey() decorator.

Different stores

This service takes advantage of cache-manager under the hood. The cache-manager package supports a wide-range of useful stores, for example, Redis store. A full list of supported stores is available here. To set up the Redis store, simple pass the package together with corresponding options to the register() method.

  2. import * as redisStore from 'cache-manager-redis-store';
  3. import { CacheModule, Module } from '@nestjs/common';
  4. import { AppController } from './app.controller';
  6. @Module({
  7.   imports: [
  8.     CacheModule.register({
  9.       store: redisStore,
  10.       host: 'localhost',
  11.       port: 6379,
  12.     }),
  13.   ],
  14.   controllers: [AppController],
  15. })
  16. export class ApplicationModule {}

Adjust tracking

By default, Nest uses the request URL (in an HTTP app) or cache key (in websockets and microservices apps, set through the @CacheKey() decorator) to associate cache records with your endpoints. Nevertheless, sometimes you might want to set up tracking based on different factors, for example, using HTTP headers (e.g. Authorization to properly identify profile endpoints).

In order to accomplish that, create a subclass of CacheInterceptor and override the trackBy() method.

  2. @Injectable()
  3. class HttpCacheInterceptor extends CacheInterceptor {
  4.   trackBy(context: ExecutionContext): string | undefined {
  5.     return 'key';
  6.   }
  7. }

Async configuration

You may want to asynchronously pass in module options instead of passing them statically at compile time. In this case, use the registerAsync() method, which provides several ways to deal with async configuration.

One approach is to use a factory function:

  2. CacheModule.registerAsync({
  3.   useFactory: () => ({
  4.     ttl: 5,
  5.   }),
  6. });

Our factory behaves like all other asynchronous module factories (it can be async and is able to inject dependencies through inject).

  2. CacheModule.registerAsync({
  3.   imports: [ConfigModule],
  4.   useFactory: async (configService: ConfigService) => ({
  5.     ttl: configService.getString('CACHE_TTL'),
  6.   }),
  7.   inject: [ConfigService],
  8. });

Alternatively, you can use the useClass method:

  2. CacheModule.registerAsync({
  3.   useClass: CacheConfigService,
  4. });

The above construction will instantiate CacheConfigService inside CacheModule and will use it to get the options object. The CacheConfigService has to implement the CacheOptionsFactory interface in order to provide the configuration options:

  2. @Injectable()
  3. class CacheConfigService implements CacheOptionsFactory {
  4.   createCacheOptions(): CacheModuleOptions {
  5.     return {
  6.       ttl: 5,
  7.     };
  8.   }
  9. }

If you wish to use an existing configuration provider imported from a different module, use the useExisting syntax:

  2. CacheModule.registerAsync({
  3.   imports: [ConfigModule],
  4.   useExisting: ConfigService,
  5. });

This works the same as useClass with one critical difference - CacheModule will lookup imported modules to reuse any already-created ConfigService, instead of instantiating its own.