Cost optimization (read/write reduction) in Firebase - Commands & Configuration

Introduction

Firebase charges based on how many times your app reads and writes data. Reducing these operations helps lower your bill while keeping your app fast and responsive.

When your app has many users reading the same data repeatedly.

When you want to avoid unnecessary writes that don't change data.

When you want to cache data locally to reduce network calls.

When you want to batch multiple writes into one operation.

When you want to listen only to specific data changes instead of the whole database.

Commands

This command fetches your current Firestore security rules to check if you can optimize reads by restricting access.

Terminal

firebase firestore:rules:get

Expected Output

service cloud.firestore {

  match /databases/{database}/documents {

    match /{document=**} {

      allow read, write: if false;

    }

  }

}

Deploy updated Firestore rules that limit reads and writes to only necessary data, reducing costs.

Terminal

firebase deploy --only firestore:rules

Expected Output

=== Deploying to project my-firebase-project ===



✔  firestore: rules updated successfully



✔  Deploy complete!

→

--only - Deploy only Firestore rules without affecting other services

List your Firestore indexes to ensure queries are efficient and do not cause extra reads.

Terminal

firebase firestore:indexes

Expected Output

No composite indexes defined.

Check logs of Cloud Functions that may be causing unnecessary reads or writes.

Terminal

firebase functions:log

Expected Output

2024-06-01T12:00:00.000Z myFunction: Read 10 documents

2024-06-01T12:01:00.000Z myFunction: Write 1 document

Key Concept

If you remember nothing else from this pattern, remember: reducing unnecessary reads and writes directly lowers your Firebase costs.

Common Mistakes

Reading entire collections instead of specific documents

This causes many more reads than needed, increasing costs and slowing your app.

Query only the documents you need using filters or document IDs.

Writing data on every user action without checking if data changed

Unnecessary writes increase your billing and can cause extra reads for listeners.

Check if data changed before writing, or batch writes together.

Listening to large data sets with real-time listeners when not needed

Real-time listeners keep reading data continuously, increasing costs.

Use one-time reads or limit listeners to small data subsets.

Summary

Use Firestore security rules to restrict reads and writes to only necessary data.

Query specific documents or filtered data instead of entire collections.

Check and reduce unnecessary writes by verifying data changes before saving.