Cache invalidation strategies in Redis - Mini Project: Build & Apply

Cache Invalidation Strategies with Redis

📖 Scenario: You are building a web application that uses Redis as a cache to speed up data retrieval. To keep the cache data fresh and accurate, you need to implement cache invalidation strategies.Imagine you have a product catalog where product details are stored in a database, and you cache product information in Redis to reduce database load.

🎯 Goal: Build a Redis cache setup that stores product data, sets a time-to-live (TTL) for automatic expiration, and implements a manual cache invalidation method to remove outdated cache entries.

📋 What You'll Learn

Create Redis keys for product data with exact names

Set a TTL (time-to-live) of 300 seconds on cached product keys

Implement a manual cache invalidation command to delete a specific product cache key

Use Redis commands exactly as specified

💡 Why This Matters

🌍 Real World

Web applications use Redis caching to speed up data access and reduce database load. Cache invalidation keeps data fresh and consistent.

💼 Career

Understanding cache invalidation with Redis is essential for backend developers, DevOps engineers, and system architects working on scalable, high-performance applications.

1

Create product cache keys with data

Use the Redis SET command to create three product cache keys with these exact names and values: product:101 with value "Apple iPhone 14", product:102 with value "Samsung Galaxy S22", and product:103 with value "Google Pixel 7".

Redis

# Your Redis commands here

Hint

Use the SET command followed by the key and value in quotes.

2

Set TTL for product cache keys

Use the Redis EXPIRE command to set a time-to-live of 300 seconds on each product cache key: product:101, product:102, and product:103.

Redis

SET product:101 "Apple iPhone 14"
SET product:102 "Samsung Galaxy S22"
SET product:103 "Google Pixel 7"
# Your EXPIRE commands here

Hint

Use the EXPIRE command with the key and the TTL in seconds.

3

Manually invalidate a product cache key

Use the Redis DEL command to manually delete the cache key product:102 to invalidate its cached data.

Redis

SET product:101 "Apple iPhone 14"
SET product:102 "Samsung Galaxy S22"
SET product:103 "Google Pixel 7"
EXPIRE product:101 300
EXPIRE product:102 300
EXPIRE product:103 300
# Your DEL command here

Hint

Use the DEL command followed by the key name to remove it from cache.

4

Complete cache invalidation setup

Add a Redis SET command to update the cache for product:102 with the new value "Samsung Galaxy S22 Ultra" and reset its TTL to 300 seconds using EXPIRE.

Redis

SET product:101 "Apple iPhone 14"
SET product:102 "Samsung Galaxy S22"
SET product:103 "Google Pixel 7"
EXPIRE product:101 300
EXPIRE product:102 300
EXPIRE product:103 300
DEL product:102
# Your SET and EXPIRE commands here

Hint

Use SET to update the key and EXPIRE to reset the TTL.

Practice

1. What is the main purpose of cache invalidation in Redis?

easy

A. To keep cached data fresh and accurate

B. To increase the size of the cache

C. To slow down data retrieval

D. To permanently store data without changes

Solution

1. Step 1: Understand cache invalidation

   Cache invalidation means removing or updating cached data to avoid stale information.

2. Step 2: Identify the main goal

   The goal is to keep the cached data fresh and accurate so users get the latest information.

3. Final Answer:

   To keep cached data fresh and accurate -> Option A

4. Quick Check:

   Cache invalidation = fresh data [OK]

Hint: Cache invalidation means keeping data fresh [OK]

Common Mistakes:

• Thinking cache invalidation increases cache size
• Believing it slows down data retrieval
• Assuming cache data never changes

2. Which Redis command is used to manually delete a cached key for invalidation?

easy

A. EXPIRE

B. GET

C. SETEX

D. DEL

Solution

1. Step 1: Identify commands for cache invalidation

   Manual invalidation requires deleting keys, so the command must remove keys.

2. Step 2: Match command to action

   DEL command deletes keys immediately, while EXPIRE sets a timeout, SETEX sets value with expiration, GET retrieves value.

3. Final Answer:

   DEL -> Option D

4. Quick Check:

   Delete key = DEL command [OK]

Hint: DEL deletes keys instantly for invalidation [OK]

Common Mistakes:

• Confusing EXPIRE with immediate deletion
• Using GET which only reads data
• Thinking SETEX deletes keys

3. Consider this Redis usage:
SET user:1 "Alice" EX 10
What happens after 10 seconds?

medium

A. The key user:1 remains forever

B. The key user:1 is deleted automatically

C. The key user:1 value changes to null

D. The key user:1 expires but stays in memory

Solution

1. Step 1: Understand the EX option in SET

   EX 10 means the key expires after 10 seconds automatically.

2. Step 2: Identify what happens on expiration

   When a key expires, Redis deletes it from memory automatically.

3. Final Answer:

   The key user:1 is deleted automatically -> Option B

4. Quick Check:

   EX sets expiration = auto delete [OK]

Hint: EX sets auto-delete time for keys [OK]

Common Mistakes:

• Thinking key stays forever after expiration
• Believing value changes to null instead of deletion
• Assuming expired keys remain in memory

4. You wrote this Redis command to expire a key:
EXPIRE user:2 0
What is the problem with this command?

medium

A. It sets expiration to zero seconds, effectively deleting the key

B. It deletes the key immediately

C. It sets the key to never expire

D. It causes a syntax error

Solution

1. Step 1: Understand EXPIRE with zero seconds

   EXPIRE key 0 removes any existing expiration timeout (equivalent to PERSIST command).

2. Step 2: Identify the problem

   The intent was to expire the key, but this sets it to never expire instead.

3. Final Answer:

   It sets the key to never expire -> Option C

4. Quick Check:

   EXPIRE 0 = remove expiration [OK]

Hint: EXPIRE 0 removes expiration (never expire) [OK]

Common Mistakes:

• Thinking it deletes the key immediately
• Believing it causes a syntax error
• Assuming zero seconds expires immediately

5. You want to keep cached product data fresh but avoid deleting keys too often. Which strategy best balances speed and data correctness in Redis?

hard

A. Use a long expiration time and rely on manual invalidation when data changes

B. Never expire keys and update them only manually

C. Delete keys immediately after every read

D. Set a short expiration time and manually delete keys on updates

Solution

1. Step 1: Understand trade-offs of expiration and manual deletion

   Short expiration causes frequent reloads; manual deletion alone risks stale data.

2. Step 2: Choose balanced approach

   Long expiration reduces reloads, manual invalidation on updates keeps data correct without overhead.

3. Final Answer:

   Use a long expiration time and rely on manual invalidation when data changes -> Option A

4. Quick Check:

   Balance speed and correctness = long expiry + manual invalidation [OK]

Hint: Long expiry plus manual delete balances freshness and speed [OK]

Common Mistakes:

• Choosing very short expiration causing overhead
• Never expiring keys causing stale data
• Deleting keys after every read causing slow performance