Why Rate limiting with express-rate-limit? - Purpose & Use Cases

The Big Idea

What if a simple tool could stop bad traffic from crashing your website instantly?

The Scenario

Imagine your website suddenly gets flooded with hundreds of requests every second from the same user or bot, trying to overload your server.

You try to block them manually by checking each request and counting how many times they hit your server.

The Problem

Manually tracking and blocking repeated requests is slow and complicated.

You might miss some requests or accidentally block good users.

It's easy to make mistakes that crash your server or let attacks slip through.

The Solution

The express-rate-limit library automatically counts requests per user and blocks them when they exceed limits.

This protects your server smoothly without extra code or errors.

Before vs After

✗ Before

let count = 0;
app.use((req, res, next) => {
  count++;
  if (count > 100) res.status(429).send('Too many requests');
  else next();
});

✓ After

import rateLimit from 'express-rate-limit';
const limiter = rateLimit({ windowMs: 60000, max: 100 });
app.use(limiter);

What It Enables

You can easily protect your app from overload and abuse, keeping it fast and reliable for all users.

Real Life Example

A popular online store uses rate limiting to stop bots from spamming their checkout page, ensuring real customers can buy without delays.

Key Takeaways

Manual request tracking is error-prone and hard to maintain.

express-rate-limit automates request counting and blocking.

This keeps your server safe and responsive under heavy traffic.

Practice

1. What is the main purpose of using express-rate-limit in an Express app?

easy

A. To handle database connections efficiently

B. To speed up the server response time

C. To automatically restart the server on code changes

D. To limit the number of requests a user can make in a time window

Solution

1. Step 1: Understand the purpose of rate limiting

   Rate limiting is used to protect the server by restricting how many requests a user can send in a short time.

2. Step 2: Identify what express-rate-limit does

   This package helps set these limits easily in Express apps.

3. Final Answer:

   To limit the number of requests a user can make in a time window -> Option D

4. Quick Check:

   Rate limiting = limit requests [OK]

Hint: Rate limiting controls request count per time window [OK]

Common Mistakes:

• Thinking it speeds up server responses
• Confusing it with server restart tools
• Assuming it manages database connections

2. Which of the following is the correct way to import and use express-rate-limit in an Express app?

easy

A. const rateLimit = require('express-rate-limit'); app.use(rateLimit({ windowMs: 60000, max: 5 }));

B. const rateLimit = require('express-rate-limit'); app.use(rateLimit());

C. import rateLimit from 'express-rate-limit'; app.use(rateLimit());

D. import rateLimit from 'express-rate-limit'; app.use(rateLimit);

Solution

1. Step 1: Check import style for CommonJS

   Using require is correct for many Express apps.

2. Step 2: Verify usage of rateLimit function with options

   We must call rateLimit with an options object like { windowMs: 60000, max: 5 } to set limits.

3. Final Answer:

   const rateLimit = require('express-rate-limit'); app.use(rateLimit({ windowMs: 60000, max: 5 })); -> Option A

4. Quick Check:

   Import + call with options = B [OK]

Hint: Call rateLimit with options object, not empty or missing [OK]

Common Mistakes:

• Forgetting to call rateLimit as a function
• Using import without proper setup
• Passing rateLimit directly without options

3. Given this code snippet, what will happen if a user sends 7 requests within 1 minute?

const rateLimit = require('express-rate-limit');
const limiter = rateLimit({ windowMs: 60000, max: 5 });
app.use(limiter);

medium

A. All 7 requests will be accepted without any limit

B. Only the first 2 requests will be accepted; the rest will be blocked

C. Only the first 5 requests will be accepted; the next 2 will be blocked

D. The server will crash after 5 requests

Solution

1. Step 1: Understand the max and windowMs settings

   The limit is 5 requests per 60000 milliseconds (1 minute).

2. Step 2: Analyze the request count

   The first 5 requests are allowed; requests 6 and 7 exceed the limit and get blocked.

3. Final Answer:

   Only the first 5 requests will be accepted; the next 2 will be blocked -> Option C

4. Quick Check:

   max 5 requests = C [OK]

Hint: Requests over max in windowMs get blocked [OK]

Common Mistakes:

• Assuming all requests pass without limit
• Thinking limit resets before 1 minute
• Believing server crashes on limit

4. Identify the error in this code snippet for rate limiting:

const rateLimit = require('express-rate-limit');
const limiter = rateLimit({ max: 10 });
app.use(limiter);

medium

A. Incorrect import statement for express-rate-limit

B. Missing windowMs option to define the time window

C. Using max instead of limit option

D. Calling app.use before defining limiter

Solution

1. Step 1: Check required options for rateLimit

   The windowMs option is needed to specify the time frame for the limit.

2. Step 2: Identify missing option

   The code only sets max but does not set windowMs, so the time window is undefined.

3. Final Answer:

   Missing windowMs option to define the time window -> Option B

4. Quick Check:

   windowMs missing = A [OK]

Hint: Always set windowMs with max for rateLimit [OK]

Common Mistakes:

• Forgetting windowMs causes no time limit
• Confusing max with limit option
• Wrong import syntax

5. You want to apply rate limiting only to the login route to prevent brute force attacks. Which code snippet correctly applies express-rate-limit only to /login?

hard

A. app.use('/login', rateLimit({ windowMs: 60000, max: 5 }));

B. app.use(rateLimit({ windowMs: 60000, max: 5 })); app.use('/login');

C. app.get('/login', rateLimit({ windowMs: 60000, max: 5 }));

D. app.post(rateLimit({ windowMs: 60000, max: 5 }), '/login');

Solution

1. Step 1: Understand how to apply middleware to specific routes

   Using app.use('/login', middleware) applies the middleware only to the /login path.

2. Step 2: Check the correct syntax for rateLimit middleware

   Calling rateLimit with options returns middleware to pass to app.use.

3. Final Answer:

   app.use('/login', rateLimit({ windowMs: 60000, max: 5 })); -> Option A

4. Quick Check:

   Middleware on route = A [OK]

Hint: Use app.use with path and rateLimit middleware [OK]

Common Mistakes:

• Calling app.use without path for specific routes
• Using app.get or app.post incorrectly with middleware
• Passing middleware after route string