Data modeling best practices in Firebase - Commands & Configuration

Introduction

Data modeling in Firebase helps organize your app's data so it is easy to find and update. Good data models prevent slow app performance and complicated code.

When you want to store user profiles and their posts separately but linked.

When you need to quickly get a list of items without loading unnecessary details.

When you want to avoid repeating the same data in many places to save space.

When you want to update data in one place and have it reflect everywhere.

When you want your app to scale smoothly as more users join.

Config File - firestore.rules

firestore.rules

rules_version = '2';
service cloud.firestore {
  match /databases/{database}/documents {
    match /users/{userId} {
      allow read, write: if request.auth != null && request.auth.uid == userId;
    }
    match /posts/{postId} {
      allow read: if true;
      allow write: if request.auth != null && request.auth.uid == request.resource.data.authorId;
    }
  }
}

This file sets security rules for Firestore data access.

The /users/{userId} path allows only the logged-in user to read and write their own profile.

The /posts/{postId} path allows anyone to read posts but only the author can write or update their posts.

Commands

This command initializes Firestore in your Firebase project, setting up necessary files and configuration.

Terminal

firebase init firestore

Expected Output

=== Firestore Setup ===

✔ Firestore rules file created at firestore.rules

✔ Firestore indexes file created at firestore.indexes.json

Firebase initialization complete.

→

--project - Specify the Firebase project to initialize Firestore for

This command deploys your Firestore rules and indexes to the Firebase project, making your data model rules active.

Terminal

firebase deploy --only firestore

Expected Output

=== Deploying to 'my-firebase-project'...

✔  firestore.rules: Firestore rules deployed successfully

✔  firestore.indexes.json: Firestore indexes deployed successfully

✔  Deploy complete!

→

--only - Deploy only Firestore related configuration

This command lists the current Firestore indexes, helping you verify your data model supports efficient queries.

Terminal

firebase firestore:indexes

Expected Output

Current Firestore indexes:

Collection Group: posts

  Fields:

    authorId Ascending

    createdAt Descending

  State: READY

Key Concept

If you remember nothing else from this pattern, remember: organize your data to avoid duplication and enable fast queries by structuring collections and documents thoughtfully.

Common Mistakes

Storing all data in one big document instead of splitting into collections and documents.

This causes slow reads and writes because Firestore loads entire documents even if you need only part of the data.

Split data into smaller documents and collections to load only what you need.

Duplicating data in many places without a plan.

It makes updates complicated and can cause inconsistent data if one copy is changed but others are not.

Use references or IDs to link data instead of copying it.

Not setting proper security rules for data access.

Anyone could read or write data they shouldn't, risking privacy and data integrity.

Write rules that check user identity and limit access accordingly.

Summary

Initialize Firestore with firebase init firestore to set up your data model files.

Deploy your Firestore rules and indexes with firebase deploy --only firestore to enforce data access and optimize queries.

Check your Firestore indexes with firebase firestore:indexes to ensure your data model supports efficient queries.