Let’s say you’re counting the number of cities in a country, so you register an onDocumentCreated trigger for:

All my Firestore write and read operations are stored like a queue internally when there is low internet. How to handle this queue.

I am quite new to firestore, so my question might be very obvious.

DIRECTORY=”./STORAGE” firebase emulators:start –import $DIRECTORY –export-on-exit $DIRECTORY $@ The above works just fine to export the default database, but that’s not the one I have in use. A custom database is being used instead for development and I’d like to persist all that storage to resume where I last left off. Would this be automated […]

The scenario

Trying to implement a default Firestore DB into my Remix web application that integrates with Shopify Hydrogen, and the getDocs query (getDocs(collection(db, “products”))) returns a snapshot with no documents. I have followed the documentation almost verbatim. I know this is not a connection issue as the reads are going through to Firestore, and I get a querySnapshot with the relevant Firestore information.

Considering a collection in Cloud Firestore on which we do the following three queries:

Initially I found firestore appealing because it lets you organize your data hierarchically, and this matches more closely how my data behaves in the real world. However while, yes, nominally firestore lets you organize data hierarchically, functionally it is almost the same as storing everything in big flat collections:

Initially I found firestore appealing because it lets you organize your data hierarchically, and this matches more closely my intuition on how my data is organized. However while, yes, nominally firestore lets you organize data hierarchically, functionally it is almost the same as storing everything in big flat collections:

In Firestore or Realtime Database, how many active users can listen for changes to the same document simultaneously? For instance, if 1000 users are subscribed to updates on a single field within a document, will all users reliably receive notifications when that field is updated? Are there any limits to the number of listeners per document or per field, especially in terms of scalability?