There are three areas where cost is associated
Operations: All reads, writes, and deletes have a cost associated with them. Reads include queries, simple fetches, and updates through realtime listeners.
Storage : You're charged for the data you store in Cloud Firestore, including metadata and indexes. Examples of metadata include document names, collection IDs, and field names. Index entries typically include the collection ID, the field values indexed, and the document name.
Network bandwidth: Outgoing network bandwidth (or network egress, respectively) costs include connection overhead for your Cloud Firestore requests.
factors affecting are: Daily Active Users (DAU)
https://firebase.google.com/pricing => this gives overall pricing. Having quoted a high volume such as 1M, better to go with Blaze plan. It is also possible to start with Spark or Flame during dev and then move to Blaze.
To compute the actual volume of data & operations that get billed, we might need to get an insight into the Daily Active Users (DAU) of the total install base. The below links provide samples of total read/write/function calls and its cost considering 10% of DAU. However, these may not be very precise as the data usage depend on per app and which feature is mostly used.
https://cloud.google.com/functions/pricing
https://cloud.google.com/firestore/docs/billing-example
https://cloud.google.com/incident-response/#pricing => In alpha phase, so for free at this point
Operations: All reads, writes, and deletes have a cost associated with them. Reads include queries, simple fetches, and updates through realtime listeners.
Storage : You're charged for the data you store in Cloud Firestore, including metadata and indexes. Examples of metadata include document names, collection IDs, and field names. Index entries typically include the collection ID, the field values indexed, and the document name.
Network bandwidth: Outgoing network bandwidth (or network egress, respectively) costs include connection overhead for your Cloud Firestore requests.
factors affecting are: Daily Active Users (DAU)
https://firebase.google.com/pricing => this gives overall pricing. Having quoted a high volume such as 1M, better to go with Blaze plan. It is also possible to start with Spark or Flame during dev and then move to Blaze.
To compute the actual volume of data & operations that get billed, we might need to get an insight into the Daily Active Users (DAU) of the total install base. The below links provide samples of total read/write/function calls and its cost considering 10% of DAU. However, these may not be very precise as the data usage depend on per app and which feature is mostly used.
https://cloud.google.com/functions/pricing
https://cloud.google.com/firestore/docs/billing-example
https://cloud.google.com/incident-response/#pricing => In alpha phase, so for free at this point
No comments:
Post a Comment