How to NOT get a 30K Firebase Bill
Why Stack Overflow recommends it
Stack Overflow users link it when Firestore read quotas or scaling and pricing worries come up in questions about querying and structuring Firebase data.
Recommended by 2 people across 2 different months, 2018 to 2018.
What it is
A Fireship video on keeping Firebase costs under control, prompted by a real story of a team that ran up a roughly 30K USD bill in under 72 hours. It covers both client-side and server-side optimizations for the Realtime Database and Firestore.
What people said
Recommends Angus · 2018-08 · Stack Overflow · on “Firebase - Server Side Function onUpdate()”
Referring to the MongoDB NoSQL Documentation [LINK] : Scalability is not just about speed . It's about 3 different metrics, which often work together: Cluster Scale. Distributing the database across 100+ nodes, often in multiple data centers Performance Scale . Sustaining 100,000+ database read and writes per second while maintaining strict latency SLAs Data Scale . Storing 1 billion+ documents in the database In Firebase Database (Realtime DB / Cloud Firestore), performance and scalability are not issues even the database has grown towards billions of documents. NoSQL databases support auto-sharding , meaning that they natively and automatically spread data across an arbitrary number of ser
Recommends Jesse Lima · 2018-12 · Stack Overflow · on “How to create the following data structure in a NoSQL environment”
Firestore has a different approach to the NoSQL world. Once you know the data you will use (as You already do) there are some very important points about what architecture the data will have. And It depends a lot about how the data grows, what kind of queries you will need and how often you will use them. Some cases You can create a root collection that aggregates data and queries might be easier. There is a great video from Firebase Channel that might help. Check it out! How to Structure Your Data | Get to Know Cloud Firestore #5 [LINK] [UPDATED] December 26th Others videos that might help to model and query your data is these videos: How to Connect Firebase Users to their Data - 3 Methods
Cites Kyle · 2018-10 · Stack Overflow · on “How to refresh streambuilder in firestore query?”
I'm trying to create a list of cards, those cards take information from Firestore a query (need .where ) it all worked out until I passed my quota, a bit later I found out about this: [this video] . I need to read specific documents with .where and post them in a streambuilder, I've thought of multiple options (mostly around Future, JSON) which non of them worked. I've theoretically thought of somehow pausing a streambuilder and reenabling it every pull-to-refresh or making a quota through a futurebuilder but I had no luck. Here's my code: Code [LINK] I couldn't find an efficient way to do this, any luck anyone?