Data denormalization strategies in Firebase - Commands & Configuration

Introduction

When you build apps with Firebase, you often need to store data in a way that makes it fast and easy to get what you want. Data denormalization means copying some data in more than one place to avoid slow lookups and complex joins.

When you want your app to load data quickly without waiting for many database calls.

When you have related data that changes rarely but is read often, like user profiles shown in many places.

When you want to avoid complex queries that Firebase Realtime Database or Firestore can't do easily.

When you want to keep your app simple by reading all needed data in one go.

When you want to reduce costs by minimizing the number of database reads.

Commands

This command creates or updates a user document with basic info. We start by adding the main data.

Terminal

firebase firestore:documents:set users/user123 '{"name": "Alice", "age": 30}'

Expected Output

✔  Document users/user123 has been created/updated.

Here we create a post document that includes the author's name copied from the user document. This is denormalization to avoid extra lookups when showing posts.

Terminal

firebase firestore:documents:set posts/post456 '{"title": "Hello World", "authorId": "user123", "authorName": "Alice"}'

Expected Output

✔  Document posts/post456 has been created/updated.

We fetch the post document to see the denormalized author name directly without needing to fetch the user document separately.

Terminal

firebase firestore:documents:get posts/post456

Expected Output

{

  "title": "Hello World",

  "authorId": "user123",

  "authorName": "Alice"

}

We update the user document with a new name and age. This shows that when data changes, you must also update all copies to keep data consistent.

Terminal

firebase firestore:documents:set users/user123 '{"name": "Alice Smith", "age": 31}'

Expected Output

✔  Document users/user123 has been created/updated.

We update the post document's denormalized author name to match the updated user name. This manual sync is part of denormalization strategy.

Terminal

firebase firestore:documents:set posts/post456 '{"title": "Hello World", "authorId": "user123", "authorName": "Alice Smith"}'

Expected Output

✔  Document posts/post456 has been created/updated.

Key Concept

If you remember nothing else from this pattern, remember: denormalization means copying data in multiple places to make reads faster but requires careful updates to keep data consistent.

Common Mistakes

Not updating all copies of denormalized data when the original changes.

This causes inconsistent data shown in the app, confusing users and causing bugs.

Always update every place where the data is copied, either manually or with automated functions.

Denormalizing too much data without a clear plan.

This makes updates complicated and increases the chance of errors.

Only denormalize data that is read often and changes rarely.

Trying to do complex joins or queries instead of denormalizing.

Firebase databases are not designed for complex joins, causing slow or impossible queries.

Design your data structure with denormalization to avoid complex queries.

Summary

Use denormalization to copy important data in multiple places for faster reads.

Update all copies of denormalized data when the original changes to keep consistency.

Avoid complex queries by designing your data with denormalization in mind.