Key naming conventions (colons for namespacing) in Redis - Step-by-Step Execution

Concept Flow - Key naming conventions (colons for namespacing)

Start with base key

↓

Add colon ':' separator

↓

Add namespace segment

↓

Repeat colon + segment as needed

↓

Final key formed

↓

Use key in Redis commands

This flow shows how Redis keys are built by joining parts with colons to create namespaces for better organization.

Execution Sample

Redis

SET user:1000:name "Alice"
GET user:1000:name
SET user:1000:email "[e-mail]"
GET user:1000:email

This code sets and gets Redis keys using colons to separate namespaces like 'user' and '1000'.

Execution Table

Step	Command	Key Used	Action	Result
1	SET user:1000:name "Alice"	user:1000:name	Store value 'Alice'	OK
2	GET user:1000:name	user:1000:name	Retrieve value	"Alice"
3	SET user:1000:email "[e-mail]"	user:1000:email	Store value '[e-mail]'	OK
4	GET user:1000:email	user:1000:email	Retrieve value	"[e-mail]"
5	END	-	No more commands	Execution complete

💡 All commands executed; keys used with colons to separate namespaces.

Variable Tracker

Key	Initial	After Step 1	After Step 3	Final
user:1000:name	null	"Alice"	"Alice"	"Alice"
user:1000:email	null	null	"[e-mail]"	"[e-mail]"

Key Moments - 2 Insights

Why do we use colons ':' in Redis keys?

Colons act as separators to create namespaces, making keys easier to organize and find, as shown in steps 1 and 3 where keys like 'user:1000:name' are used.

Can Redis keys have spaces instead of colons?

While Redis keys can technically have spaces, using colons is a common convention for clarity and to avoid confusion, as demonstrated in the execution_table keys.

Visual Quiz - 3 Questions

Look at the execution table, what value is stored at step 1 for key 'user:1000:name'?

A "Alice"

B "[e-mail]"

C null

D "Bob"

💡 Hint

Check the 'Result' column in row 1 of the execution_table.

At which step is the key 'user:1000:email' first set?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the 'Command' and 'Key Used' columns in the execution_table.

If we replaced colons ':' with dashes '-' in keys, what would change in the execution_table?

A Values stored would change

B Keys would show dashes instead of colons in the 'Key Used' column

C Commands would fail to execute

D No change at all

💡 Hint

Consider how keys are displayed in the 'Key Used' column and Redis key naming rules.

Concept Snapshot

Redis keys use colons ':' to separate parts, creating namespaces.
Example: user:1000:name stores a user's name.
This helps organize keys logically.
Commands use full keys with colons.
Colons are just characters, no special Redis meaning.
Use consistent naming for clarity.

Full Transcript

In Redis, keys are named using colons ':' to separate different parts, like namespaces. This helps keep keys organized, for example 'user:1000:name' stores the name of user 1000. Commands like SET and GET use these full keys. The colon is just a character used to separate parts, making keys easier to read and manage. This visual shows setting and getting keys with colons, tracking values stored and retrieved step-by-step.

Practice

1. Why do Redis keys often use colons (:) in their names?

easy

A. To encrypt the key names for security

B. To make keys shorter and save memory

C. To organize keys into logical groups like folders

D. To separate keys by data type automatically

Solution

1. Step 1: Understand Redis key naming

   Redis keys are simple strings, but using colons helps group related keys logically.

2. Step 2: Recognize the purpose of colons

   Colons act like folder separators, making it easier to find and manage keys.

3. Final Answer:

   To organize keys into logical groups like folders -> Option C

4. Quick Check:

   Colons = logical grouping [OK]

Hint: Colons separate key parts like folders in a path [OK]

Common Mistakes:

• Thinking colons shorten keys
• Believing colons encrypt keys
• Assuming colons change data types

2. Which of the following is the correct Redis key name using colons for namespacing?

easy

A. user1000profile

B. user:1000:profile

C. user_1000_profile

D. user-1000-profile

Solution

1. Step 1: Identify proper colon usage

   Redis keys use colons to separate logical parts, like 'user', '1000', and 'profile'.

2. Step 2: Compare options

   Only user:1000:profile uses colons correctly to namespace the key.

3. Final Answer:

   user:1000:profile -> Option B

4. Quick Check:

   Colons separate key parts correctly [OK]

Hint: Look for colons separating key parts clearly [OK]

Common Mistakes:

• Using dashes or underscores instead of colons
• Not separating parts at all
• Mixing separators inconsistently

3. Given these Redis keys:
user:1000:name
user:1000:email
user:1001:name
Which command will return all keys for user 1000?

medium

A. KEYS user:1000:*

B. KEYS user:*:name

C. KEYS user:1001:*

D. KEYS *:email

Solution

1. Step 1: Understand the key pattern

   Keys for user 1000 start with 'user:1000:' followed by any suffix.

2. Step 2: Match the pattern with the command

   The command 'KEYS user:1000:*' matches all keys starting with 'user:1000:'.

3. Final Answer:

   KEYS user:1000:* -> Option A

4. Quick Check:

   Pattern matches user 1000 keys [OK]

Hint: Use * wildcard after user:1000: to get all keys [OK]

Common Mistakes:

• Using wrong user ID in pattern
• Using wildcard in wrong position
• Confusing name and email keys

4. You have keys named session:1234 and session-1234. You want to list all session keys using KEYS session:* but it returns only session:1234. What is the issue?

medium

A. The command syntax is incorrect

B. Redis does not support dashes in keys

C. Keys with dashes are automatically deleted

D. Keys with dashes are not matched by colon wildcard

Solution

1. Step 1: Understand pattern matching

   The pattern 'session:*' matches keys starting with 'session:' only, not 'session-'.

2. Step 2: Identify why keys with dashes are missed

   Keys with dashes do not match the colon separator pattern, so they are excluded.

3. Final Answer:

   Keys with dashes are not matched by colon wildcard -> Option D

4. Quick Check:

   Colon wildcard matches only colon keys [OK]

Hint: Wildcards match exact separators; dashes differ from colons [OK]

Common Mistakes:

• Thinking dashes are invalid in Redis keys
• Assuming command syntax is wrong
• Believing keys with dashes get deleted

5. You want to store user data in Redis with keys for profile and settings. Which key naming scheme best follows Redis conventions for easy management?

hard

A. user:1000:profile and user:1000:settings

B. user1000profile and user1000settings

C. user-profile-1000 and user-settings-1000

D. profile:user:1000 and settings:user:1000

Solution

1. Step 1: Identify clear namespacing

   Using 'user:1000' as a prefix groups all user data logically.

2. Step 2: Check key suffixes for data types

   'profile' and 'settings' as suffixes clearly describe the data stored.

3. Step 3: Compare options

   user:1000:profile and user:1000:settings uses colons consistently for namespacing and clarity.

4. Final Answer:

   user:1000:profile and user:1000:settings -> Option A

5. Quick Check:

   Consistent colon namespacing = user:1000:profile and user:1000:settings [OK]

Hint: Use user:id:data_type format with colons [OK]

Common Mistakes:

• Not using colons for clear separation
• Mixing order of parts inconsistently
• Using ambiguous key names