Cloud Firestore Data Modeling
summary
Cloud Firestore indexes every field and serves queries in time proportional to the result set, not the dataset, so designs favor read-fast denormalized records but must respect limits: 1 MB document limit, 40,000 index fields, and roughly 1 write/sec per document. Menu items work best as subcollections to avoid sending huge documents; cross-subcollection searches require collection group queries. Billing is driven by documents touched, and server-side Cloud Functions are recommended to keep denormalized copies in sync safely.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:26Firebase
- 2:45Sequel
- 5:43No Sequel
- 9:21Documents Collections
- 15:15Menu
- 15:31Subcollection
- 15:50Document Limits
- 18:29Only Fetch Documents
- 18:47Data Usage
- 20:44Billing
- 21:54Is this bad
- 22:13Manual action
- 22:55One right answer
- 24:46Indexed documents
- 26:08Subcollections
- 26:42Collection Group Queries
- 31:28Security Rules
- 32:06Orders
- 34:09Duplicate Data
- 34:30Normalize Data
- 36:53Client Order
- 37:15Cloud Functions
- 39:19Get to Know Firestore
- 39:56Conclusion
related talks
41mUsing Cloud Firestore to Build Planetary Scale Apps
40mLet’s get Fired up: Getting started with Firebase Firestore
37mBuilding Scalable Apps with Cloud Firestore
01mCloud Firestore updates from Firebase Summit #Shorts
18mCloud Firestore for Game Developers
59mData Modeling for
42mCapacity vs Efficiency: Building a Globally Scalable Cloud Database
13mAdvanced offline caching techniques in Cloud Firestore
