Rate limiter with INCR and EXPIRE in Redis - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the INCR command in Redis when implementing a rate limiter?

INCR increments the value of a key by one. In rate limiting, it counts the number of requests made by a user or client within a time window.

beginner

Why do we use the EXPIRE command alongside INCR in Redis for rate limiting?

EXPIRE sets a time-to-live (TTL) on the key so that the count resets after a fixed time window, allowing the rate limiter to enforce limits per time period.

intermediate

How does combining INCR and EXPIRE help prevent race conditions in a Redis rate limiter?

By using INCR atomically and setting EXPIRE only when the key is new, Redis ensures accurate counting without conflicts even with concurrent requests.

beginner

What happens if EXPIRE is not set on the Redis key used for rate limiting?

The count will never reset, causing the user to be permanently blocked after reaching the limit once, which is incorrect behavior.

intermediate

Explain the typical request flow for a rate limiter using Redis INCR and EXPIRE.

1. Client sends request.
2. Server runs INCR on a key representing the client.
3. If key is new, EXPIRE is set to define the time window.
4. If count exceeds limit, request is rejected.
5. Otherwise, request proceeds.

What does the Redis INCR command do in a rate limiter?

A Sets the expiration time for a key

B Increments the request count for a client

C Deletes the key after a timeout

D Resets the request count to zero

INCR increases the count of requests made by a client, helping track usage.

Why is the EXPIRE command important in Redis rate limiting?

A It blocks requests permanently

B It increments the count

C It resets the count after a time window

D It creates a new key

EXPIRE sets a time limit so the count resets, allowing rate limits per time period.

What happens if you call INCR on a non-existing key in Redis?

A Redis creates the key with value 1

B Redis returns an error

C Redis sets the key to 0

D Nothing happens

INCR creates the key with initial value 1 if it does not exist.

How can you ensure EXPIRE is only set once when using INCR for rate limiting?

A Set EXPIRE only if INCR returns 1

B Set EXPIRE every time INCR is called

C Set EXPIRE before INCR

D Do not use EXPIRE

If INCR returns 1, the key is new, so set EXPIRE once to start the time window.

What is a common problem if EXPIRE is not used in a Redis rate limiter?

A Requests are never blocked

B INCR command fails

C Redis crashes

D Request counts never reset, causing permanent blocking

Without EXPIRE, counts accumulate indefinitely, blocking users permanently after limit.

Describe how Redis INCR and EXPIRE commands work together to implement a rate limiter.

Think about counting requests and resetting counts after some time.

Explain the request flow and key management in a Redis-based rate limiter using INCR and EXPIRE.

Focus on how Redis commands control counting and timing.

Practice

1. What is the main purpose of using the INCR command in a Redis rate limiter?

easy

A. To increase the count of actions performed by a user

B. To set the expiration time for a key

C. To delete a key from Redis

D. To reset the count to zero

Solution

1. Step 1: Understand the role of INCR in counting

   The INCR command increments the integer value stored at a key by one, which is used to count user actions.

2. Step 2: Differentiate from other commands

   Commands like EXPIRE set timeouts, and DEL deletes keys, but INCR specifically increases counts.

3. Final Answer:

   To increase the count of actions performed by a user -> Option A

4. Quick Check:

   INCR counts actions = A [OK]

Hint: INCR always adds 1 to a key's value [OK]

Common Mistakes:

• Confusing INCR with EXPIRE
• Thinking INCR resets counts
• Assuming INCR deletes keys

2. Which Redis command syntax correctly sets a key to expire after 60 seconds?

easy

A. EXPIRE key '60s'

B. EXPIRE 60 key

C. EXPIRE key 60

D. SETEX key 60 value

Solution

1. Step 1: Recall EXPIRE command syntax

   The correct syntax is EXPIRE key seconds, where seconds is an integer.

2. Step 2: Evaluate options

   EXPIRE key 60 matches the syntax. EXPIRE 60 key reverses arguments. SETEX key 60 value is a different command combining SET and EXPIRE. EXPIRE key '60s' uses invalid string format for seconds.

3. Final Answer:

   EXPIRE key 60 -> Option C

4. Quick Check:

   EXPIRE key seconds = D [OK]

Hint: EXPIRE command uses key then seconds [OK]

Common Mistakes:

• Swapping key and seconds arguments
• Using string with units for seconds
• Confusing SETEX with EXPIRE

3. Given the following Redis commands executed in order:

INCR user:123
EXPIRE user:123 10
INCR user:123
TTL user:123

What will the TTL user:123 command return immediately after these commands?

medium

A. 10

B. 9 or less

C. -1

D. 0

Solution

1. Step 1: Analyze command sequence

   First INCR creates or increments the key. Then EXPIRE sets TTL to 10 seconds. Another INCR increments the count but does not reset TTL.

2. Step 2: Understand TTL behavior

   TTL counts down from 10 seconds after EXPIRE. The second INCR does not affect TTL, so TTL will be less than or equal to 9 seconds depending on execution time.

3. Final Answer:

   9 or less -> Option B

4. Quick Check:

   TTL after EXPIRE and INCR = B [OK]

Hint: INCR does not reset TTL, so TTL decreases over time [OK]

Common Mistakes:

• Assuming INCR resets TTL
• Expecting TTL to remain exactly 10
• Confusing TTL -1 (no expire) with positive TTL

4. You implemented a rate limiter using INCR and EXPIRE, but the count never resets after the expiration time. What is the most likely cause?

medium

A. The key was deleted manually before expiration

B. INCR command resets the TTL unintentionally

C. Redis server is out of memory

D. EXPIRE was never set on the key

Solution

1. Step 1: Identify why count doesn't reset

   If the count never resets, it means the key never expired, so the expiration was not set properly.

2. Step 2: Evaluate other options

   INCR does not reset TTL, manual deletion would remove the key, and out of memory causes errors but not this behavior.

3. Final Answer:

   EXPIRE was never set on the key -> Option D

4. Quick Check:

   No EXPIRE means no reset = C [OK]

Hint: Always set EXPIRE once to enable automatic reset [OK]

Common Mistakes:

• Assuming INCR resets TTL
• Ignoring that EXPIRE must be set
• Blaming Redis memory issues incorrectly

5. You want to implement a rate limiter that allows 100 requests per user per minute using Redis with INCR and EXPIRE. Which approach is best to avoid resetting the expiration time on every request?

hard

A. Set EXPIRE only when INCR returns 1

B. Call EXPIRE every time after INCR

C. Use SETEX instead of INCR

D. Delete the key manually after 60 seconds

Solution

1. Step 1: Understand TTL reset problem

   Calling EXPIRE every time resets TTL, causing the window to slide indefinitely, which is incorrect for fixed window rate limiting.

2. Step 2: Best practice for setting EXPIRE

   Set EXPIRE only when the key is created (when INCR returns 1), so TTL counts down properly without resetting.

3. Final Answer:

   Set EXPIRE only when INCR returns 1 -> Option A

4. Quick Check:

   Set EXPIRE once at first INCR = A [OK]

Hint: Set EXPIRE only on first INCR to avoid TTL reset [OK]

Common Mistakes:

• Resetting EXPIRE on every request
• Using SETEX which overwrites count
• Manually deleting keys instead of TTL