Successfully reducing Firestore read operations
summary
Shows how billing is traced to Firestore reads using the Google Cloud Billing console and group by SKU and how custom Google Cloud Monitoring dashboards and alerts (example thresholds and overlaying Cloud Functions instances) reveal spikes. Demonstrates parsing audit logs (methods listen runQuery get batch) with a Python script to find that ~80% of cost comes from real-time listeners, then applies limits pagination offline persistence and precomputed stats tables so reads drop and billing stabilizes.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:03Firestore read pricing
- 7:17Read operation sources
- 13:25Audit logs insights
- 18:21Efficient queries and caching
- 23:08Real-time listeners and writes
- 24:37Summary
related talks
42mCapacity vs Efficiency: Building a Globally Scalable Cloud Database
04mTop 5 takeaways
01mCloud Firestore updates from Firebase Summit #Shorts
44mA Crash Course in Google Analytics for Firebase and BigQuery
41mUsing Cloud Firestore to Build Planetary Scale Apps
28mFirebase analytics for BigQuery
24mHoney, I shrunk the bill!
37mBuilding Scalable Apps with Cloud Firestore