Key design patterns in Redis - Mini Project: Build & Apply

Redis Key Design Patterns

📖 Scenario: You are building a simple user session management system using Redis. Redis stores data as keys and values, and how you design your keys is very important for easy access and maintenance.In this project, you will create keys following common Redis key design patterns to store user session data.

🎯 Goal: Build Redis keys using common design patterns to store and organize user session information clearly and efficiently.

📋 What You'll Learn

Create keys using a clear naming pattern with colons as separators

Use a prefix to group related keys

Include user IDs in keys to identify user-specific data

Store session data as simple string values

Demonstrate how to set and get these keys

💡 Why This Matters

🌍 Real World

Redis key design patterns help organize data clearly, making it easy to find and manage user sessions or other grouped data in real applications.

💼 Career

Understanding key design is essential for backend developers and database administrators working with Redis to build scalable and maintainable systems.

1

Create user session keys with prefixes

Create three Redis keys for user sessions with the prefix session and user IDs 1001, 1002, and 1003. The keys should be named exactly as session:1001, session:1002, and session:1003. Assign each key a string value representing the session token: token_abc, token_def, and token_ghi respectively.

Redis

# Your code here to create keys session:1001, session:1002, session:1003 with their tokens

Hint

Use the SET command to create keys with the pattern session:userID.

2

Add a configuration key for session expiration time

Create a Redis key named config:session_timeout and set its value to 3600 to represent session expiration time in seconds.

Redis

SET session:1001 token_abc
SET session:1002 token_def
SET session:1003 token_ghi
# Your code here to set config:session_timeout to 3600

Hint

Use the SET command with the key config:session_timeout and value 3600.

3

Retrieve a user session token using the key

Write a Redis command to get the session token for user ID 1002 using the key session:1002.

Redis

SET session:1001 token_abc
SET session:1002 token_def
SET session:1003 token_ghi
SET config:session_timeout 3600
# Your code here to get the value of session:1002

Hint

Use the GET command with the key session:1002 to retrieve the token.

4

Set expiration for user session keys

Add expiration of 3600 seconds to each user session key: session:1001, session:1002, and session:1003 using the EXPIRE command.

Redis

SET session:1001 token_abc
SET session:1002 token_def
SET session:1003 token_ghi
SET config:session_timeout 3600
GET session:1002
# Your code here to set expiration 3600 on session:1001, session:1002, session:1003

Hint

Use the EXPIRE command with each session key and the timeout value 3600.

Practice

1. What is the main purpose of using key design patterns in Redis?

easy

A. To delete all keys automatically

B. To organize data for easy access and management

C. To slow down data retrieval

D. To increase the size of the database

Solution

1. Step 1: Understand Redis key design patterns

   Key design patterns help organize Redis keys logically.

2. Step 2: Identify the main benefit

   Organizing keys makes data easier to access and manage efficiently.

3. Final Answer:

   To organize data for easy access and management -> Option B

4. Quick Check:

   Key design patterns = organize data [OK]

Hint: Think about why organization helps in real life [OK]

Common Mistakes:

• Confusing organization with database size
• Assuming patterns slow down Redis
• Thinking patterns delete keys automatically

2. Which of the following is a correct Redis key pattern to group user data by user ID?

easy

A. user:1234:name

B. user-1234-name

C. user1234name

D. user/1234/name

Solution

1. Step 1: Identify common Redis key pattern syntax

   Redis keys often use colons ':' as separators for readability and grouping.

2. Step 2: Compare options

   user:1234:name uses colons to separate user, ID, and attribute clearly.

3. Final Answer:

   user:1234:name -> Option A

4. Quick Check:

   Colon separators = correct pattern [OK]

Hint: Use colons to separate parts of keys [OK]

Common Mistakes:

• Using dashes or slashes which are less common
• Not separating parts clearly
• Combining all parts without separators

3. Given these Redis keys: order:1001:status, order:1002:status, and order:1001:items, which command retrieves the status of order 1002?

medium

A. GET order:1001:items

B. GET order:1002:items

C. GET order:1002:status

D. GET order:1001:status

Solution

1. Step 1: Identify the key for order 1002 status

   The key format is order:<order_id>:status, so for 1002 it is order:1002:status.

2. Step 2: Match the command to the key

   GET order:1002:status retrieves the status of order 1002.

3. Final Answer:

   GET order:1002:status -> Option C

4. Quick Check:

   Correct key = order:1002:status [OK]

Hint: Match key parts exactly to get correct data [OK]

Common Mistakes:

• Mixing order IDs in keys
• Using wrong attribute like items instead of status
• Confusing similar keys

4. You have keys like session-123 and session:124. Why might this inconsistency cause problems?

medium

A. Redis will merge both keys automatically

B. Redis will throw a syntax error

C. Keys with dashes are not allowed in Redis

D. It breaks pattern consistency, making data harder to manage

Solution

1. Step 1: Understand key pattern consistency

   Consistent key patterns help group and find related data easily.

2. Step 2: Analyze the impact of mixed separators

   Using both dashes and colons breaks this consistency, causing confusion.

3. Final Answer:

   It breaks pattern consistency, making data harder to manage -> Option D

4. Quick Check:

   Inconsistent keys = management issues [OK]

Hint: Always use one separator style consistently [OK]

Common Mistakes:

• Thinking Redis forbids dashes
• Expecting syntax errors from mixed separators
• Assuming Redis merges keys automatically

5. You want to store product reviews in Redis for multiple products and users. Which key design pattern is best to efficiently group reviews by product and user?

hard

A. review:<product_id>:<user_id>

B. <product_id>-review-<user_id>

C. review<product_id><user_id>

D. review/<product_id>/<user_id>

Solution

1. Step 1: Identify clear, scalable key pattern

   Using colons to separate product and user IDs groups reviews logically.

2. Step 2: Evaluate options for clarity and consistency

   review:<product_id>:<user_id> uses colons and a prefix 'review' for easy filtering and management.

3. Final Answer:

   review:<product_id>:<user_id> -> Option A

4. Quick Check:

   Colon-separated keys = best practice [OK]

Hint: Use prefixes and colons to group related data [OK]

Common Mistakes:

• Using ambiguous separators like dashes or slashes
• Combining parts without separators
• Not using a clear prefix for grouping