Embedding vs referencing in Redis - Quick Revision & Key Differences

Recall & Review

beginner

What does embedding mean in Redis data modeling?

Embedding means storing related data together inside a single Redis data structure, like a hash or JSON document, so you can get all related info in one go.

beginner

What is referencing in Redis?

Referencing means storing related data separately and linking them by keys or IDs, so you fetch related data in multiple steps.

beginner

Name one advantage of embedding data in Redis.

Embedding lets you get all related data in one fast read, which is simple and efficient for small or tightly related data.

intermediate

Why might you choose referencing over embedding in Redis?

You choose referencing when data is large, shared, or changes often, so you avoid duplicating data and keep updates simple.

intermediate

Give a real-life example of embedding vs referencing in Redis.

Embedding: Store a user's profile and their settings together in one hash. Referencing: Store user info in one key and their orders in separate keys linked by user ID.

What is a key benefit of embedding data in Redis?

A Fewer reads to get all related data

B Easier to update shared data

C Less memory used for large data

D Data is always normalized

Embedding stores related data together, so you can get it all with one read.

When is referencing preferred over embedding in Redis?

A When data is small and simple

B When you want to avoid using keys

C When you want faster single reads

D When data is large or shared by many

Referencing helps avoid duplicating large or shared data by linking separate keys.

Which Redis data structure is commonly used for embedding related data?

A String

B Set

C Hash

D List

Hashes let you store multiple fields and values together, good for embedding.

What is a downside of referencing in Redis?

A Data duplication

B More reads needed to get full data

C Hard to update shared data

D Cannot link data by keys

Referencing requires multiple reads to gather all related data.

Which scenario fits embedding best in Redis?

A User profile with a few settings

B Large product catalog shared by many

C Orders linked to many users

D Frequently changing shared data

Embedding is good for small, tightly related data like user profile and settings.

Explain the difference between embedding and referencing in Redis with simple examples.

Think about storing data together vs storing data separately and linking.

When would you choose embedding over referencing in Redis and why?

Consider data size, sharing, and read performance.

Practice

1. Which statement best describes embedding in Redis?

easy

A. Storing related data together in one key.

B. Storing data in separate keys linked by IDs.

C. Using multiple databases for related data.

D. Storing only references without actual data.

Solution

1. Step 1: Understand embedding concept

   Embedding means putting related data inside one Redis key, so all data is together.

2. Step 2: Compare with referencing

   Referencing stores data separately and links them by IDs, which is different from embedding.

3. Final Answer:

   Storing related data together in one key. -> Option A

4. Quick Check:

   Embedding = data together [OK]

Hint: Embedding means one key holds all related data [OK]

Common Mistakes:

• Confusing embedding with referencing
• Thinking embedding uses multiple keys
• Assuming embedding stores only IDs

2. Which Redis data structure is best suited for embedding small related data together?

easy

A. Sorted Set

B. String

C. List

D. Hash

Solution

1. Step 1: Identify data structure for embedding

   Hashes store multiple fields and values inside one key, ideal for embedding related small data.

2. Step 2: Compare other structures

   Strings hold single values, Lists and Sorted Sets are for ordered collections, less suited for embedding small related fields.

3. Final Answer:

   Hash -> Option D

4. Quick Check:

   Embedding small data = Hash [OK]

Hint: Use Hash for embedding small related fields [OK]

Common Mistakes:

• Choosing String for multiple fields
• Confusing List with Hash
• Using Sorted Set without score relevance

3. Given these Redis commands:

HSET user:100 name "Alice" age 30
HSET user:100:address city "NY" zip 10001

Which describes the data design?

medium

A. Referencing address data in a separate key

B. Embedding all user data in one key

C. Using a List to store user info

D. Storing user data as a String

Solution

1. Step 1: Analyze keys and data

   user:100 holds name and age, user:100:address holds address fields separately.

2. Step 2: Identify design pattern

   Address is stored in a separate key linked by user ID, which is referencing.

3. Final Answer:

   Referencing address data in a separate key -> Option A

4. Quick Check:

   Separate keys linked by ID = referencing [OK]

Hint: Separate keys with related IDs mean referencing [OK]

Common Mistakes:

• Thinking all data is embedded in one key
• Confusing List with Hash usage
• Assuming address is embedded inside user key

4. You want to store user profiles with embedded address data in Redis using hashes. Which command has an error?

medium

A. HSET user:200 name "Bob" age 25

B. HSET user:200:address city "LA" zip 90001

C. HSET user:200 name "Bob" city "LA" zip 90001

D. HSET user:200 name "Bob" age 25 city "LA" zip 90001

Solution

1. Step 1: Check embedding address in user hash

   Embedding means all fields in one key, so address fields city and zip should be in user:200 hash.

2. Step 2: Identify error in command C

   Command C uses a separate key user:200:address, storing address separately linked by ID. This is referencing, not embedding.

3. Final Answer:

   HSET user:200:address city "LA" zip 90001 -> Option B

4. Quick Check:

   Separate keys = referencing, not embedding [OK]

Hint: Embedding: all data in ONE key, no sub-keys [OK]

Common Mistakes:

• Missing value for a field
• Using separate keys when embedding
• Mixing field-value pairs incorrectly

5. You have a Redis database storing product info. You want to optimize for fast reads of product details including reviews. Which design is best?

hard

A. Embed product details and all reviews in one hash key per product.

B. Store all reviews in a single list key for all products.

C. Store product details in one hash and each review in separate keys linked by product ID.

D. Store product details as strings and reviews as sorted sets.

Solution

1. Step 1: Consider data size and access pattern

   Reviews can be many and large, embedding all in one key can cause large data and slow updates.

2. Step 2: Choose referencing for scalability

   Storing product details separately and reviews in linked keys allows efficient updates and reads without large keys.

3. Step 3: Evaluate other options

   Embedding all reviews in one hash risks large keys; storing all reviews in a single list key for all products mixes products; storing product details as strings and reviews as sorted sets don't fit review structure well.

4. Final Answer:

   Store product details in one hash and each review in separate keys linked by product ID. -> Option C

5. Quick Check:

   Large related data = referencing for performance [OK]

Hint: Large or many related items? Use referencing [OK]

Common Mistakes:

• Embedding large lists causing slow reads
• Mixing all reviews in one key
• Ignoring update frequency of reviews