Cache-aside pattern in Redis - Mini Project: Build & Apply

Implementing Cache-Aside Pattern with Redis

📖 Scenario: You are building a simple product information service. To improve performance, you want to use Redis as a cache to store product details temporarily. When a product is requested, the system should first check Redis cache. If the product is not found in cache, it should fetch from the main database (simulated here), store it in Redis, and then return the data.

🎯 Goal: Build a cache-aside pattern using Redis commands to fetch product data. You will create a product data dictionary, configure a Redis key prefix, implement the cache lookup and fallback to database retrieval, and finally set the cache expiration time.

📋 What You'll Learn

Create a dictionary called product_db with exact product entries.

Create a string variable called cache_key_prefix with the exact value 'product:'.

Write a Redis command to check if a product key exists in cache and if not, get it from product_db and set it in Redis.

Set the cache expiration time to exactly 300 seconds for the cached product data.

💡 Why This Matters

🌍 Real World

This pattern is used in web applications to speed up data retrieval by caching frequently accessed data in Redis.

💼 Career

Understanding cache-aside pattern is essential for backend developers and database engineers to optimize application performance.

1

Create the product database dictionary

Create a dictionary called product_db with these exact entries: '101': 'Red T-shirt', '102': 'Blue Jeans', '103': 'Black Sneakers'.

Redis

# Create the product_db dictionary with product IDs and names
# Your code here

Hint

Use curly braces to create a dictionary with keys as strings and values as strings.

2

Set the Redis cache key prefix

Create a string variable called cache_key_prefix and set it to the exact value 'product:'.

Redis

product_db = {'101': 'Red T-shirt', '102': 'Blue Jeans', '103': 'Black Sneakers'}
# Create cache_key_prefix variable with value 'product:'
# Your code here

Hint

Assign the string 'product:' to the variable cache_key_prefix.

3

Implement cache lookup and fallback to database

Write Redis commands to check if the key cache_key_prefix + '101' exists. If it does, get the value. If not, get the product from product_db['101'], set it in Redis with the key, and then get it.

Redis

product_db = {'101': 'Red T-shirt', '102': 'Blue Jeans', '103': 'Black Sneakers'}
cache_key_prefix = 'product:'
# Use Redis commands to check cache and fallback to product_db
# Your code here

Hint

Use redis.exists() to check key, redis.get() to get value, and redis.set() to store value.

4

Set cache expiration time

Add a Redis command to set the expiration time of the key cache_key_prefix + '101' to exactly 300 seconds after setting the product in cache.

Redis

product_db = {'101': 'Red T-shirt', '102': 'Blue Jeans', '103': 'Black Sneakers'}
cache_key_prefix = 'product:'

# Check if product is in cache
if redis.exists(cache_key_prefix + '101'):
    product = redis.get(cache_key_prefix + '101')
else:
    product = product_db['101']
    redis.set(cache_key_prefix + '101', product)
    # Set expiration time to 300 seconds
    # Your code here

Hint

Use redis.expire(key, seconds) to set the expiration time.

Practice

1. What is the main idea behind the cache-aside pattern in Redis?

easy

A. Automatically update cache whenever the database changes without application intervention

B. Load data into cache only when the application requests it and cache misses occur

C. Preload all data into cache before any application requests

D. Use cache only for temporary data that does not come from the database

Solution

1. Step 1: Understand cache-aside pattern basics

   The cache-aside pattern means the application loads data into cache only when it is needed, not before.

2. Step 2: Compare options with this concept

   Load data into cache only when the application requests it and cache misses occur matches this idea exactly, while others describe different caching strategies.

3. Final Answer:

   Load data into cache only when the application requests it and cache misses occur -> Option B

4. Quick Check:

   Cache-aside = Load on demand [OK]

Hint: Cache-aside means load cache only on demand [OK]

Common Mistakes:

• Thinking cache is preloaded with all data
• Assuming cache updates automatically without app logic
• Confusing cache-aside with write-through caching

2. Which Redis command is typically used to check if a key exists in cache before loading from the database in cache-aside pattern?

easy

A. DEL

B. GET

C. SET

D. EXISTS

Solution

1. Step 1: Identify command to check key presence

   In Redis, EXISTS checks if a key is present in cache.

2. Step 2: Match commands with their purpose

   GET retrieves value, SET stores value, DEL deletes key. Only EXISTS checks presence.

3. Final Answer:

   EXISTS -> Option D

4. Quick Check:

   Check key presence = EXISTS [OK]

Hint: Use EXISTS to check if cache key is present [OK]

Common Mistakes:

• Using GET to check existence (GET returns null if missing)
• Confusing SET with checking commands
• Using DEL which deletes keys

3. Consider this Redis cache-aside pseudocode:

if not redis.exists('user:123'):
    data = db.query('SELECT * FROM users WHERE id=123')
    redis.set('user:123', data)
else:
    data = redis.get('user:123')

What happens if the key user:123 is missing in Redis?

medium

A. Redis automatically loads data from database

B. Data is fetched from Redis but will be empty

C. Data is fetched from the database and stored in Redis cache

D. An error occurs because key does not exist

Solution

1. Step 1: Analyze the if condition for cache miss

   If user:123 does not exist in Redis, the code queries the database for data.

2. Step 2: Understand cache population after miss

   After fetching from database, it stores the data in Redis with set for future requests.

3. Final Answer:

   Data is fetched from the database and stored in Redis cache -> Option C

4. Quick Check:

   Cache miss triggers DB fetch and cache store [OK]

Hint: Cache miss means fetch DB and store in cache [OK]

Common Mistakes:

• Assuming Redis auto-loads data from DB
• Expecting error on missing key
• Thinking Redis returns empty data silently

4. You have this cache-aside code snippet in Redis:

if redis.get('product:456') is None:
    data = db.query('SELECT * FROM products WHERE id=456')
    redis.set('product:456', data)
else:
    data = redis.get('product:456')

But the cache never updates even after database changes. What is the likely problem?

medium

A. The cache is never invalidated or updated after DB changes

B. The Redis GET command is incorrect

C. The database query syntax is wrong

D. The key name 'product:456' is invalid in Redis

Solution

1. Step 1: Identify cache update mechanism

   The code only sets cache if key is missing but does not update or invalidate cache after DB changes.

2. Step 2: Understand cache staleness cause

   Without cache invalidation or update logic after DB writes, cache remains stale and does not reflect DB changes.

3. Final Answer:

   The cache is never invalidated or updated after DB changes -> Option A

4. Quick Check:

   Cache stale if no invalidation after DB update [OK]

Hint: Cache must be invalidated after DB updates [OK]

Common Mistakes:

• Assuming GET command causes update
• Blaming DB query syntax without evidence
• Thinking Redis keys are invalid without reason

5. You want to implement cache-aside pattern in Redis for a user profile service. Which approach correctly handles cache misses and updates when user data changes?

1. On read: check cache, if miss fetch DB and set cache
2. On write: update DB, then delete cache key to force reload on next read

Why is deleting the cache key after DB update preferred over updating cache directly?

hard

A. Deleting cache key avoids race conditions and stale data issues

B. Updating cache directly is impossible in Redis

C. Deleting cache key improves Redis memory usage drastically

D. Updating cache directly causes Redis to crash

Solution

1. Step 1: Understand cache update strategies

   Deleting cache key after DB update forces next read to reload fresh data, avoiding stale cache.

2. Step 2: Recognize race condition prevention

   Direct cache update risks race conditions if multiple writes/read happen concurrently; deleting key is safer.

3. Final Answer:

   Deleting cache key avoids race conditions and stale data issues -> Option A

4. Quick Check:

   Delete cache key after DB write to avoid stale data [OK]

Hint: Delete cache key after DB update to avoid stale data [OK]

Common Mistakes:

• Thinking Redis cannot update cache values
• Believing direct cache update is always better
• Assuming deleting cache key crashes Redis