Rate limiting with express-rate-limit - Step-by-Step Execution

Concept Flow - Rate limiting with express-rate-limit

Client sends request

↓

express-rate-limit middleware

↓

Check request count for IP

↓

Send 429

When a client sends a request, the middleware checks how many requests that IP made. If the limit is exceeded, it sends a 429 error. Otherwise, it lets the request continue.

Execution Sample

Express

import rateLimit from 'express-rate-limit';

const limiter = rateLimit({
  windowMs: 60000,
  max: 3
});

app.use(limiter);

This code limits each IP to 3 requests per 60 seconds using express-rate-limit middleware.

Execution Table

Step	Request Number	IP Request Count	Condition (count > max?)	Action	Response
1	1	1	1 > 3? No	Allow request	200 OK
2	2	2	2 > 3? No	Allow request	200 OK
3	3	3	3 > 3? No	Allow request	200 OK
4	4	4	4 > 3? Yes	Block request	429 Too Many Requests

💡 At step 4, the request count exceeds max (4 > 3), so the request is blocked with 429.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4
IP Request Count	0	1	2	3	4

Key Moments - 2 Insights

Why does the 4th request get blocked even though the max is 3?

Because the middleware counts requests starting from 1, so when the count reaches 4, it exceeds the max of 3, triggering the block as shown in execution_table step 4.

Does the rate limit reset automatically?

Yes, after the windowMs time (60 seconds here), the count resets to 0, allowing new requests. This is implied by the windowMs setting in the code sample.

Visual Quiz - 3 Questions

Look at the execution table, what is the IP Request Count at step 3?

A 4

B 2

C 3

D 1

💡 Hint

Check the 'IP Request Count' column at step 3 in the execution_table.

At which request number does the condition become true and block the request?

A 4

B 3

C 2

D 1

💡 Hint

Look at the 'Condition' column in execution_table where it changes from No to Yes.

If max was changed to 5, what would happen at request number 4?

A Request 4 would be blocked

B Request 4 would be allowed

C Request 4 would cause an error

D Request 4 would reset the count

💡 Hint

Compare the 'max' value in the code sample and the condition logic in execution_table.

Concept Snapshot

express-rate-limit middleware limits requests per IP.
Set windowMs (time window) and max (max requests).
Middleware counts requests per IP.
If count > max, sends 429 error.
Otherwise, request proceeds normally.

Full Transcript

Rate limiting with express-rate-limit works by counting how many requests a client IP makes within a set time window. The middleware checks this count on each request. If the count exceeds the max allowed, it blocks the request with a 429 Too Many Requests response. Otherwise, it lets the request continue. The count resets after the time window expires. This helps protect servers from too many requests from one client.

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