Is there a way to take incremental backups for firestore? We need to take regular backups and taking full backup everyday will only get more expensive over time.
Also is there any plan of supporting point in time restore for firestore?
Firestore does not have a backup mechanism. It has an import/export mechanism, which is not really the same thing. If you need backups, especially incremental backups, you will need to implement that yourself or find another solution.
Related
Import and Export helps make it easier to run backups in Firestore as described here
Backing up a Firestore database means a read for every document. That seems incredibly expensive.
Similarly, it would seemingly cost highly when trying to restore a backup.
Is there any way to run these backups without having to incur such high costs?
Creating a backup of your documents requires reading those documents. There is currently no way to create a backup without (charged) reading of each document.
I am using firebase realtime database.
The project works like a chat application.
We are constantly downloading / uploading.
But the cost seems too high. All data is downloaded again every get 1 message. What can I do to reduce the cost of this?
Instead of downloading data again every time I think of creating a cache. What should we pay attention to when creating the cache?
What are the solutions Firebase offers to reduce cost for realtime database?
Thanks, best regards
The pricing page of Firebase is pretty clear. The cost for the Realtime Database is based on:
The amount of data you store in the database.
The amount of data that is read from the database.
So those are the two factors you'll need to pay attention to if you want to reduce the cost.
Which one has the highest impact really depends on where your cost is coming from, which you didn't say. But the most common one is to look if you can reduce the number of times each client downloads the same data by local caching. If you're using the native mobile SDKs for iOS and Android (which you also don't mention), you can often already accomplish some reduction by enabling disk caching.
Quick question please. I am working on an on-demand app that uses live tracking which would require the constant update of people’s lat and lng, and I plan to you Firebase Firestore for it. Having read a few scary articles (lol scary in terms of costing) about how Cost shoot up overnight while using firestore. I’d like to know if it’s advisable to use firestore for this, as I think the entire BaaS it offers covers everything I need. If you can recommend the best approach possible to this, thanks
It depends on how large is your userbase and how frequently you want to update their current location.
Under the Flame Plan ($25/month) 100k document writes per day for firestore is supported. If you want more than that you'll need Blaze Plan (pay as you go).
See the pricing for details:
https://firebase.google.com/pricing
I'm starting a project with Cloud Firestore and I added my first collections and documents.
In order to be sure to use the right tool, I tried to search if there were limitations with Cloud Firestore.
I saw there were some limitations in bandwidth, number of commits etc.. but I didn't find (or didn't understand) if there was a limitation with the size of the database (number of collections / documents).
Is there a limitation? If yes, does it exist plans/bundles to extend those limitations ?
Best Regards,
Cloud Firestore scales effortlessly. It will store as much data as you're willing to put into it (and pay for). Practically speaking, volume of data is not a concern.
I was wondering if it was possible and also, if someone can give his testimony of using both. Actually, for me, the real time thing is not that important, I care more about the NoSQL Database. I really care about pricing and I can see that Firebase prices are okay for almost everything (authentication is even free), but database is very expensive in my opinion (5$/giga stored and 1$/Giga downloaded ...). That's why I want to use DynamoDB for the database because it's way cheaper.
What do you think?
Finally, Firebase just released a new NoSQL service that is somehow similar to DynamoDB. No need to connect to DynamoDB anymore!