Solutions Web Application

Rate Limiting Using Throttler In NestJs

rate limiting using throttler in nestjs


Rate limiting is used to restrict users to hit an endpoint for a limited amount of time. In other words, by rate limiting we can control the number of incoming requests per time. Like we can define the user can hit an endpoint for 10 times every minute. So, if anyone hits that endpoint more than 10 times, then it will throw an error and the user can not access that URL for a limited amount of time.

Why We Need To Use Rate Limiting?

  • Rate limiting is mainly used for managing the frequency of incoming requests per duration.
  • Better server load management.
  • Reduced risk of attacks like Brute Force.
  • The server will never be overloaded by incoming API calls.

Drawbacks of Rate Limiting

As we discussed, Rate Limit handles the number of requests per specified duration, so in some cases, it may block our traffic from accessing our site.

Sometimes it may block legitimate users from accessing our site. It can not identify between legitimate and spam traffic. Due to this our real users might not be able to access our application.

Example of Rate Limiting in NestJs

In this example we will see how we can use the Throttler package for rate limiting.

Step 1

Install package:

npm i --save @nestjs/throttler

Step 2

After successful installation of package you can use ThrottlerModule just like any other module of nest. You can use this module with forRoot or forRootAsync methods. In your app.module.ts file import module like :

	imports: [
	      ttl : 60,
	      limit : 10,
export class AppModule {}

In the above code “ttl” is Time To Live, which means the amount of time at which you want to restrict the requests. And the limit is used for the amount of requests per ttl.

Step 3

After importing you need to use a guard to use this module globally.
For that you need to do like:

providers: [
     provide: APP_GUARD,
     useClass: ThrottlerGuard,

By doing this now your Rate limit is set to 10 Requests per minute for every endpoint of your project.

app.module.ts file will look like this:

import { Module } from '@nestjs/common';
import { AppController } from './app.controller';
import { AppService } from './app.service';
import { UsersModule } from './users/users.module';
import { ThrottlerModule, ThrottlerGuard } from '@nestjs/throttler';
import { APP_GUARD } from '@nestjs/core';
   imports: [UsersModule,
           ttl: 60,
           limit: 2
   providers: [AppService,
           provide: APP_GUARD,
           useClass: ThrottlerGuard
export class AppModule {}

Step 4

Now if you want to Skip some modules from Rate limiting then you need to specify SkipThrottle() function in that controller like:

export class UsersController {}

Now the rate limit will not apply to any of this controller’s route.

If you want to override “ttl” or “limit” which is set globally, then you need to mention that like:

@Throttle(3, 60)
list() {    
  return "List works with custom rate limiting.";

This will override default configurations for this specific route.

import { Controller, Get, HttpCode } from '@nestjs/common';
import { SkipThrottle, Throttle, ThrottlerGuard } from '@nestjs/throttler';
export class UsersController {
   // This route will skip rate limiting.
       return "List work without Rate limiting"

   // Rate limiting is applied to this route.
       return "List work with Rate limiting"
   // Override default configuration for Rate limiting and duration.
   @Throttle(3, 60)
       return "Get profile with custom Rate limiting."

Where We Can Use This Technique In Our App?

In any app, the most important thing is Login and Register APIs. So we need to secure those API first. So, we can apply rate limiting on the APIs like Login, Register, Forgot password etc.


Any Payment-related API – If your APP contains a Payment-related API where you are transferring some payment data then you can apply Rate Limit there to prevent attacks like Brute force.

APIs Which Are Having Large Data – We can use this where we have large Response data in API. By doing this we can restrict multiple API calls at the same time and it will optimize the server load.

Want to read more Blogs ?

Similar Post

Solutions Technology
Migrations with TypeORM in NestJs
Migrations with TypeORM in NestJs.png

Certified By


Got more questions? Chat with our experts or schedule a call back

Bot 14:41
Hi how can i help you?