Why hashes represent objects in Redis - Visual Breakdown

Concept Flow - Why hashes represent objects

Start: Create Redis Hash

↓

Add Field-Value Pairs

↓

Store as Single Key

↓

Access Fields by Name

↓

Update or Retrieve Specific Fields

↓

Hash Represents Object with Properties

This flow shows how Redis hashes store multiple field-value pairs under one key, representing an object with properties.

Execution Sample

Redis

HSET user:1000 name "Alice" age "30" city "NY"
HGET user:1000 name
HGETALL user:1000

Create a hash for user:1000 with fields name, age, city; then get the name field and all fields.

Execution Table

Step	Command	Action	Result
1	HSET user:1000 name "Alice" age "30" city "NY"	Create hash key 'user:1000' with fields	Fields set: name=Alice, age=30, city=NY
2	HGET user:1000 name	Retrieve 'name' field from hash	Alice
3	HGETALL user:1000	Retrieve all fields and values	name: Alice, age: 30, city: NY
4	HSET user:1000 age "31"	Update 'age' field to 31	Field 'age' updated to 31
5	HGETALL user:1000	Retrieve all fields after update	name: Alice, age: 31, city: NY
6	DEL user:1000	Delete the hash key	Key 'user:1000' deleted
7	HGETALL user:1000	Try to get fields from deleted key	(nil)

💡 Execution stops after key deletion; no fields exist for retrieval.

Variable Tracker

Variable	Start	After Step 1	After Step 4	After Step 6
user:1000	does not exist	{name: Alice, age: 30, city: NY}	{name: Alice, age: 31, city: NY}	does not exist

Key Moments - 3 Insights

Why does Redis use a single key with multiple fields instead of multiple keys for each property?

Because the hash stores all related fields under one key, it groups properties like an object, making access and updates efficient and organized, as shown in execution_table steps 1 and 3.

What happens when you update a field in a Redis hash?

Updating a field changes only that field's value without affecting others, as seen in step 4 where 'age' changes from 30 to 31, confirmed by step 5.

What does retrieving all fields from a hash return after deletion?

After deleting the hash key (step 6), retrieving fields returns nil (step 7), meaning the object no longer exists.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'age' after step 4?

A 31

B 30

C nil

D Error

💡 Hint

Check the 'Result' column in step 4 and step 5 for the updated 'age' value.

At which step does the hash key 'user:1000' get deleted?

A Step 3

B Step 4

C Step 6

D Step 7

💡 Hint

Look for the 'DEL' command in the 'Command' column.

If you add a new field 'email' to the hash after step 5, how would the variable_tracker change?

A The 'user:1000' variable would be deleted

B A new column 'After Step 5' with 'email' field added

C No change because fields can't be added

D The 'age' field would reset to 30

💡 Hint

Adding fields updates the hash object state, reflected in variable_tracker columns.

Concept Snapshot

Redis hashes store multiple field-value pairs under one key.
They represent objects with properties.
Use HSET to add/update fields.
Use HGET or HGETALL to retrieve fields.
Efficient for grouped data access and updates.

Full Transcript

This visual execution shows how Redis hashes represent objects by storing multiple fields under a single key. First, a hash key 'user:1000' is created with fields name, age, and city. Then, retrieving a single field or all fields shows the stored data. Updating a field changes only that field's value. Deleting the key removes the entire object. This grouping makes Redis hashes a natural way to represent objects with properties.

Practice

1. Why are Redis hashes considered similar to objects in programming?

easy

A. Because they store multiple related fields under one key, like object properties

B. Because they only store single values like simple variables

C. Because they automatically run code like functions

D. Because they store data in a list format

Solution

1. Step 1: Understand what a Redis hash stores

   A Redis hash stores multiple field-value pairs under one key, grouping related data.

2. Step 2: Compare with programming objects

   Programming objects group properties (fields) together, similar to how hashes group fields.

3. Final Answer:

   Because they store multiple related fields under one key, like object properties -> Option A

4. Quick Check:

   Hashes = grouped fields like object properties [OK]

Hint: Think of hashes as objects holding many properties [OK]

Common Mistakes:

• Confusing hashes with simple string keys
• Thinking hashes run code like functions
• Assuming hashes store lists instead of field-value pairs

2. Which of the following is the correct Redis command to set a field 'name' with value 'Alice' in a hash 'user:1'?

easy

A. HMSET user:1 name Alice

B. SET user:1 name Alice

C. HGET user:1 name Alice

D. HSET user:1 name Alice

Solution

1. Step 1: Identify the command to set a single field in a hash

   HSET sets a single field-value pair in a Redis hash.

2. Step 2: Check other commands

   SET is for strings, HMSET is deprecated, HGET retrieves values.

3. Final Answer:

   HSET user:1 name Alice -> Option D

4. Quick Check:

   Use HSET to set hash fields [OK]

Hint: Use HSET to add or update a single hash field [OK]

Common Mistakes:

• Using SET instead of HSET for hashes
• Using HGET which reads but does not set
• Using deprecated HMSET command

3. Given the Redis commands:
HSET user:2 age 30
HSET user:2 city "New York"
What will HGETALL user:2 return?

medium

A. ["user:2", "age", "30", "city", "New York"]

B. ["age", "30", "city", "New York"]

C. ["age", 30, "city", "New York"]

D. ["age", "city", "30", "New York"]

Solution

1. Step 1: Understand HGETALL output format

   HGETALL returns an array of field and value strings alternating.

2. Step 2: Match fields and values

   Fields are "age" and "city" with values "30" and "New York" as strings.

3. Final Answer:

   ["age", "30", "city", "New York"] -> Option B

4. Quick Check:

   HGETALL returns field-value pairs as strings [OK]

Hint: HGETALL returns fields and values as string pairs [OK]

Common Mistakes:

• Including the key name in the output
• Returning values as numbers instead of strings
• Mixing field and value order

4. You run the command HSET user:3 name "Bob" age 25 but get an error. What is the likely cause?

medium

A. Field names cannot be strings

B. The key 'user:3' does not exist yet

C. HSET only accepts one field-value pair at a time in this Redis version

D. Age must be a string, not a number

Solution

1. Step 1: Check HSET command syntax

   Older Redis versions allow only one field-value pair per HSET call.

2. Step 2: Analyze error cause

   Trying to set two pairs at once causes syntax error in older versions.

3. Final Answer:

   HSET only accepts one field-value pair at a time in this Redis version -> Option C

4. Quick Check:

   HSET single pair per call in older Redis [OK]

Hint: Check Redis version for multi-field HSET support [OK]

Common Mistakes:

• Assuming key must exist before HSET
• Thinking field names can't be strings
• Confusing data type requirements for values

5. You want to store user profiles with fields: 'name', 'age', and 'email' in Redis. Which approach best uses hashes to represent these profiles efficiently?

hard

A. Use a separate hash for each user with key like 'user:<id>' and fields for each property

B. Store all users in one big hash with user IDs as fields and JSON strings as values

C. Use simple string keys for each property like 'name:<id>', 'age:<id>', 'email:<id>'

D. Store user data as a list with all properties concatenated as one string

Solution

1. Step 1: Consider data organization for user profiles

   Each user should have a separate hash to group their properties clearly.

2. Step 2: Evaluate other options

   One big hash mixes users, separate strings scatter data, lists lose field names.

3. Final Answer:

   Use a separate hash for each user with key like 'user:<id>' and fields for each property -> Option A

4. Quick Check:

   Separate hashes per user = clear, efficient object representation [OK]

Hint: Use one hash per object for clear property grouping [OK]

Common Mistakes:

• Mixing all users in one hash losing clarity
• Using separate keys for each property causing scattered data
• Storing data as lists losing field names