Data denormalization strategies in Firebase - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a denormalized data structure for a user's profile in Firebase.

Firebase

const userProfile = {
  name: "Alice",
  age: 30,
  posts: [1]
};

Drag options to blanks, or click blank then click option'

A["post1", "post2"]

B"post1"

C{post1: true, post2: true}

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Using a single string instead of a list for multiple posts.

Using an object with true values which is less straightforward here.

Using an array of post IDs allows easy access to all posts related to the user, which is a common denormalization strategy.

2fill in blank

medium

Complete the code to update a user's post count in a denormalized Firebase database.

Firebase

firebase.database().ref('users/' + userId).update({
  postCount: [1]
});

Drag options to blanks, or click blank then click option'

Aposts

BpostsCount

Cposts.length

DpostCount + 1

Attempts:

3 left

💡 Hint

Common Mistakes

Using the length of posts array directly without updating.

Using an undefined variable like postsCount.

Incrementing the existing postCount by 1 keeps the denormalized count accurate after adding a new post.

3fill in blank

hard

Fix the error in the denormalized data update code to avoid overwriting unrelated data.

Firebase

firebase.database().ref('posts/' + postId).update({
  title: newTitle,
  content: newContent,
  [1]: newTimestamp
});

Drag options to blanks, or click blank then click option'

AupdatedAt

BcreatedAt

Ctimestamp

Dtime

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'createdAt' which does not change on updates.

Using generic names like 'time' which are unclear.

Using 'updatedAt' clearly indicates the time of the latest update, which is a best practice in denormalized data.

4fill in blank

hard

Fill both blanks to correctly denormalize user data and posts in Firebase.

Firebase

const denormalizedData = {
  users: {
    [1]: {
      name: userName,
      postCount: [2]
    }
  }
};

Drag options to blanks, or click blank then click option'

AuserId

BuserName

CpostCount

Dposts

Attempts:

3 left

💡 Hint

Common Mistakes

Using userName as a key instead of userId.

Using posts array instead of postCount for the count.

The userId is used as the key under 'users' to uniquely identify the user. The postCount stores the number of posts, which is a common denormalized field.

5fill in blank

hard

Fill all three blanks to correctly update denormalized post data with user info in Firebase.

Firebase

firebase.database().ref('posts/' + [1]).update({
  title: newTitle,
  authorName: [2],
  authorId: [3]
});

Drag options to blanks, or click blank then click option'

ApostId

BuserName

CuserId

DpostKey

Attempts:

3 left

💡 Hint

Common Mistakes

Using postKey instead of postId which may not be defined.

Mixing up userName and userId positions.

postId identifies the post to update. authorName and authorId store denormalized user info for quick access.

Practice

1. What is the main purpose of data denormalization in Firebase?

easy

A. To copy data for faster reading and fewer database calls

B. To reduce data storage by removing duplicates

C. To encrypt data for better security

D. To create backups automatically

Solution

1. Step 1: Understand denormalization concept

   Denormalization means copying data to make reading faster and reduce the number of database calls.

2. Step 2: Identify the main goal in Firebase context

   Firebase uses denormalization to speed up data access, not to reduce storage or encrypt data.

3. Final Answer:

   To copy data for faster reading and fewer database calls -> Option A

4. Quick Check:

   Denormalization = faster reads [OK]

Hint: Denormalization means copying data to speed up reads [OK]

Common Mistakes:

• Confusing denormalization with data encryption
• Thinking denormalization reduces storage space
• Assuming denormalization creates backups

2. Which Firebase data structure is best suited for denormalization?

easy

A. Nested arrays with repeated data

B. Encrypted blobs stored in Firestore

C. Flat JSON objects with duplicated fields

D. Single document with all data combined

Solution

1. Step 1: Review Firebase data structures

   Firebase uses JSON-like objects. Denormalization copies data into flat objects with duplicated fields for fast access.

2. Step 2: Compare options

   Nested arrays with repeated data are not ideal; single documents can be large and slow; encrypted blobs are unrelated to denormalization.

3. Final Answer:

   Flat JSON objects with duplicated fields -> Option C

4. Quick Check:

   Denormalization uses flat JSON with duplicates [OK]

Hint: Denormalization uses flat JSON with repeated fields [OK]

Common Mistakes:

• Choosing nested arrays which complicate queries
• Using single large documents that slow reads
• Confusing encryption with denormalization

3. Given this Firebase data snippet:

{
  "users": {
    "user1": {"name": "Anna", "city": "NY"},
    "user2": {"name": "Ben", "city": "LA"}
  },
  "posts": {
    "post1": {"author": "user1", "content": "Hello"},
    "post2": {"author": "user2", "content": "Hi"}
  }
}

Which denormalized structure speeds up reading posts with author names?

medium

A. { "users": { "user1": {"name": "Anna"}, "user2": {"name": "Ben"} }, "posts": {} }

B. { "posts": { "post1": {"author": "user1", "content": "Hello"}, "post2": {"author": "user2", "content": "Hi"} } }

C. { "posts": { "post1": {"authorId": "user1"}, "post2": {"authorId": "user2"} } }

D. { "posts": { "post1": {"authorName": "Anna", "content": "Hello"}, "post2": {"authorName": "Ben", "content": "Hi"} } }

Solution

1. Step 1: Understand denormalization for faster reads

   Copy author names directly into posts to avoid extra lookups when reading posts.

2. Step 2: Analyze options

   { "posts": { "post1": {"authorName": "Anna", "content": "Hello"}, "post2": {"authorName": "Ben", "content": "Hi"} } } copies author names into posts, speeding reads. Others keep references requiring extra calls.

3. Final Answer:

   { "posts": { "post1": {"authorName": "Anna", "content": "Hello"}, "post2": {"authorName": "Ben", "content": "Hi"} } } -> Option D

4. Quick Check:

   Copy data to avoid extra lookups = { "posts": { "post1": {"authorName": "Anna", "content": "Hello"}, "post2": {"authorName": "Ben", "content": "Hi"} } } [OK]

Hint: Copy related data into posts to speed reads [OK]

Common Mistakes:

• Keeping only IDs requiring extra database calls
• Removing posts data instead of denormalizing
• Not copying author names into posts

4. You denormalized user emails into multiple places in Firebase. What is a common error when updating user email?

medium

A. Forgetting to update all copies, causing inconsistent data

B. Deleting the original user record accidentally

C. Encrypting emails twice causing read errors

D. Using arrays instead of objects for user data

Solution

1. Step 1: Understand denormalization update challenges

   When data is copied, all copies must be updated to keep data consistent.

2. Step 2: Identify common mistake

   Forgetting to update all copies leads to inconsistent emails across the database.

3. Final Answer:

   Forgetting to update all copies, causing inconsistent data -> Option A

4. Quick Check:

   Missed updates cause inconsistency [OK]

Hint: Always update every copy of denormalized data [OK]

Common Mistakes:

• Updating only one copy of data
• Deleting original data by mistake
• Confusing encryption with denormalization

5. You want to denormalize product prices into order items in Firebase. Which approach best avoids stale prices when product prices change?

hard

A. Copy product price into each order item and update all order items on price change

B. Store only product IDs in order items and fetch price dynamically on read

C. Keep prices only in product records and never copy to orders

D. Use arrays to store prices inside product documents

Solution

1. Step 1: Understand denormalization trade-offs

   Copying prices into order items speeds reads but risks stale data if not updated.

2. Step 2: Choose best approach to avoid stale data

   Storing only product IDs and fetching prices dynamically on read avoids stale prices without complex updates.

3. Final Answer:

   Store only product IDs in order items and fetch price dynamically on read -> Option B

4. Quick Check:

   Fetch price dynamically to avoid stale data [OK]

Hint: Fetch prices dynamically to keep data fresh [OK]

Common Mistakes:

• Not updating copied prices causing stale data
• Copying prices without update causing stale data
• Using arrays which complicate updates