Data modeling best practices in Firebase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main goal of data modeling in Firebase?

To organize data efficiently for fast and scalable access while minimizing costs and complexity.

beginner

Why should you avoid deeply nested data structures in Firebase?

Because deeply nested data can slow down queries and make updates more complex and costly.

intermediate

What is denormalization in Firebase data modeling?

Duplicating data in multiple places to optimize read performance and reduce complex joins.

intermediate

How does Firebase handle relationships between data entities?

By using references (keys or IDs) instead of joins, since Firebase is a NoSQL database.

beginner

What is a best practice for structuring collections and documents in Firestore?

Use collections for groups of similar items and documents for individual records, keeping documents small and focused.

Which of the following is a good practice in Firebase data modeling?

A Using SQL joins to link data

B Deeply nesting data to keep it all in one place

C Denormalizing data to optimize reads

D Storing all data in a single large document

Denormalizing data helps optimize read performance in Firebase, which does not support SQL joins.

In Firebase, how do you represent relationships between data entities?

A Using foreign keys and joins

B Using references (IDs) to link documents

C Using relational tables

D Embedding all related data inside one document

Firebase uses references (IDs) to link documents because it is a NoSQL database without joins.

Why should you keep Firebase documents small and focused?

A To reduce read and write costs and improve performance

B To make the database look cleaner

C Because Firebase limits the number of documents

D To avoid using collections

Smaller documents reduce costs and improve performance when reading and writing data.

What is a disadvantage of deeply nested data in Firebase?

A It automatically creates indexes

B It makes queries faster

C It reduces storage costs

D It increases complexity and slows down updates

Deep nesting increases complexity and can slow down updates and queries.

Which Firebase feature helps optimize data access by duplicating data?

A Denormalization

B Joins

C Normalization

D Triggers

Denormalization duplicates data to optimize read performance in Firebase.

Explain the concept of denormalization in Firebase data modeling and why it is used.

Think about how copying data helps you get it faster but requires careful updates.

Describe best practices for structuring collections and documents in Firestore.

Imagine organizing files in folders and keeping each file focused.

Practice

1. What is the main reason to use collections and documents in Firestore for data modeling?

easy

A. To make data read-only for all users

B. To store all data in one big JSON object

C. To avoid using any security rules

D. To organize data in a way that is easy to query and scale

Solution

1. Step 1: Understand Firestore structure

   Firestore organizes data into collections and documents to keep data structured and easy to access.

2. Step 2: Benefits of collections and documents

   This structure allows efficient queries and scaling as your app grows.

3. Final Answer:

   To organize data in a way that is easy to query and scale -> Option D

4. Quick Check:

   Firestore uses collections/documents for scalable data [OK]

Hint: Think of collections as folders and documents as files [OK]

Common Mistakes:

• Thinking all data should be in one JSON object
• Ignoring the need for security rules
• Assuming data is read-only by default

2. Which of the following is the correct way to reference a document in Firestore?

easy

A. db.users('user123')

B. db.collection('users').doc('user123')

C. db.get('users/user123')

D. db.document('users').collection('user123')

Solution

1. Step 1: Recall Firestore syntax

   Firestore uses collection() to select a collection and doc() to select a document.

2. Step 2: Check each option

   db.collection('users').doc('user123') correctly uses collection('users').doc('user123'). Others do not follow Firestore syntax.

3. Final Answer:

   db.collection('users').doc('user123') -> Option B

4. Quick Check:

   Firestore document reference uses collection().doc() [OK]

Hint: Remember: collection() then doc() for Firestore paths [OK]

Common Mistakes:

• Using incorrect method names like get() or document()
• Swapping collection and document order
• Trying to access documents directly from db without collection

3. Given this Firestore data model:

users (collection)
  user123 (document)
    name: 'Alice'
    posts (collection)
      post1 (document)
        title: 'Hello'

What will db.collection('users').doc('user123').collection('posts').get() return?

medium

A. A list of all posts documents under user123

B. An error because posts is not a field

C. Only the user123 document data

D. All users documents with their posts

Solution

1. Step 1: Understand nested collections

   In Firestore, collections can be nested under documents. Here, posts is a subcollection under user123.

2. Step 2: What does the query do?

   The query gets all documents in the posts collection under user123, so it returns all posts documents.

3. Final Answer:

   A list of all posts documents under user123 -> Option A

4. Quick Check:

   Subcollections return their documents on get() [OK]

Hint: Subcollections are accessed by chaining collection().doc().collection() [OK]

Common Mistakes:

• Thinking subcollections are fields inside documents
• Expecting get() to return parent document data
• Assuming get() returns all users and posts together

4. You have this Firestore security rule snippet:

match /users/{userId} {
  allow read, write: if request.auth.uid == userId;
}

What is the main issue if you want users to read their posts stored in a subcollection posts under their user document?

medium

A. The rule does not cover the posts subcollection, so access is denied

B. The rule allows anyone to read posts

C. The rule allows write but not read

D. The rule only works for admin users

Solution

1. Step 1: Analyze the rule scope

   The rule matches only the /users/{userId} document, not any subcollections like posts.

2. Step 2: Effect on subcollections

   Without explicit rules for /users/{userId}/posts/{postId}, access to posts is denied by default.

3. Final Answer:

   The rule does not cover the posts subcollection, so access is denied -> Option A

4. Quick Check:

   Security rules must cover subcollections explicitly [OK]

Hint: Rules must match subcollections separately to allow access [OK]

Common Mistakes:

• Assuming parent document rules apply to subcollections
• Believing rules allow all reads by default
• Confusing read and write permissions

5. You want to design a Firestore data model for a chat app where users can have many messages. Which approach follows best practices for scalability and easy querying?

hard

A. Store all messages in a single collection with a userId field to filter messages

B. Store messages as an array field inside each user document

C. Create a messages subcollection under each user document

D. Store messages in a single document with nested objects for each message

Solution

1. Step 1: Consider scalability needs

   Storing many messages inside one document or array can cause size limits and slow queries.

2. Step 2: Use subcollections for many related items

   Creating a messages subcollection under each user document allows efficient queries and scales well.

3. Final Answer:

   Create a messages subcollection under each user document -> Option C

4. Quick Check:

   Use subcollections for large, related data sets [OK]

Hint: Use subcollections for many related items to avoid document size limits [OK]

Common Mistakes:

• Putting many items in arrays inside documents
• Using one big collection without filtering
• Storing all data in one document causing size errors