Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
What is the cost associated with Azure Cosmos DB? Does the bill depend upon the database or containers we create? Also, does the bill depend on when we read/write data to containers or starts billing from the time we create Azure Cosmos DB? If that's the case, is there an option to disable/pause Azure Cosmos DB Account in Azure?
Pricing for Cosmos DB is described pretty nicely here: https://learn.microsoft.com/en-us/azure/cosmos-db/how-pricing-works. To summarize, you are charged for the capacity you reserved as well as for storage.
To answer your specific questions:
Does the bill depend upon the database or containers we create?
Yes. The moment you create a database or a container with throughput, that capacity is reserved for you so you start paying for that whether or not you use it. Please note that you can create a database without throughput and in that case you're not charged.
Also, does the bill depend on when we read/write data to containers or
starts billing from the time we create Azure Cosmos DB?
Account creation is free. The billing starts when you create a database or a container in that account with throughput.
If that's the case, is there an option to disable/pause Azure Cosmos
DB Account in Azure?
Unfortunately no. You will need to delete the resources to stop the billing.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
I am making an account system with firebase.
I have the auth part ready.
I also want to store data for every user.
Which database should I use? Firebase Firestore or the real-time database?
Thank you!
I suggest using Firebase Firestore for storing user's data.
You could use Firebase Firestore instead of Real Time Database. As the name suggests, the Real Time database is useful for realtime data sharing. Eg: Sharing Score of one participants to another participants realtime.
Cloud Firestore support indexed queries with compound sorting and filtering. Unlike Realtime Database, Cloud Firestore allows chaining the filters and combining filter and sort on a property in a single query
Realtime Database supports deep queries with limited sorting and filtering functionality. In a single query, you can either sort or filter, not both, on a property
While the Realtime Database is just a giant JSON tree, Cloud Firestore is a little more structured
You can expect to find new query types, more robust security rules, and improved performance with some other advanced features planned for Cloud Firestore
You can set up listeners in Cloud Firestore to stream in changes in real-time
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I have an app that I want to build using Firebase which is basically a chat for users.
There are chat rooms that are temporary, meaning that after each day the rooms (and consequently all the messages) get deleted.
I see a lot of good things about Firestore, but in this case I'll be deleting potentially a lot of messages. Firestore is not only a bit iffy for deleting a bunch of stuff, but also charges for each operation (as I recall I can simply delete a node in rtdb and every children is also deleted).
So which one would be more affordable for my app?
Firestore charges are calculated per READ/WRITE operation performed. So using Firestore for large amount of reads and writes will be significantly expensive than RTDB.
Realtime Database on the other hand calculated just GB of data download and is advisable for storing temporary data in your case, since you will be creating and deleting too frequently.
For more elaboration, check out my answer here. I've also mentioned cons of using Firestore in brief there, it was a similar case.
It will be more affordable to by RTDB resources instead of Firestore if you want to update data too frequently.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I am developing android and IOS app with web backend admin support for an organisation oriented employee, tasks and issue management system. issues and the task will be posted by any public people and issue will be addressed and solved by the organization people.
my app will have dynamic keyword filtering over the new issue posting and an algorithm will keep running to identify the issue categories dynamically from the issues being posted.
my app or the search result and filters should be fast in retrieving the data and it should not affect my application performance. I didn't know which one is good to use for a case like this.
I use the Realtime database for an large iOS app that contains users, jobs for users, favourites, messages etc. So I need the database to show results in realtime as well as being reliable.
The best features for a big app like the one I have built are the
offline capabilities
If the user goes offline, the database is still responsive and persists data to the disk which resynchronises when connection is established.
Data synchronization
All of my users on the app can see changes happening instantly such as notifications and messages, job updates etc. It's reliable and stops any overlapping potential risk.
https://firebase.google.com/docs/database/
Additionally, it sounds like you will benefit from the easy JSON structure that Firebase Realtime database offers to build categories etc.
I use a lot of filters in my iOS app and the calls to the database return results almost instantly given a connection is established; its very flexible.
In terms of reliability
Cloud Firestore is currently in beta. Stability in a beta product is not always the same as that of a fully launched product, where as Realtime Database is a mature product.
Use Fire-Base Realtime database if your apps are not going to serve more than 1000 people.
Because Fire-base Realtime doesn't perform much complex and fast queries like Fire-Base FireStore. And you can not upgrade your app if your app is based on RealTime database.
FireStore has more features that Realtime database.
You can go and check the difference between both of them:-
https://firebase.google.com/docs/database/rtdb-vs-firestore
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am making an app for our school. It contains a score updating feature. i am using firebase database to update the scores. (not published yet) But firebase realtime database offers only 100 RT connections for free.
so is there a way to get more than 100 RT connections for free ? atleast by reducing other features? (like database storage, 5GB media storage..)
Firebase provides 3 plans.
When you create a project on Firebase, you start with the Spark Plan. This plan is free allowing 100 simultaneous connections, 10Gb downloaded per month, 5Gb of Storage and 1Gb for Hosting. This should be good enough for starters.
But if you want more than that, you can pay 25$ per month on the Flame Plan that gives you unlimited simultaneous connections.
Or go for the Blaze Plan which is Pay as you scale. You get unlimited simultaneous connections, and you'll only pay when your database scales.
And no. You can't get more simultaneous connections by getting rid of other services.
For more information about the plans, you can check the Pricing Tab on their website.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I am considering using firebase as a way to brodcast data messages to many connected users on mobile phone native apps running actively in the foreground.
In a "channel" (presumably a node in the database) there might be a new 1kb message every second or so and potentially thousands of users listening in.
The ideal latency should be less than a second.
Is Firebase realtime json database ideal for this use case?
What are the limitations on number of users, number of messages and latency?
How does it compare to "Google Cloud Messaging", native push notifications, or other frameworks, for the same purpose?
Firebase is a real time json data base and it would work absolutely fine for what you are requesting.
There is no limitation to the number of users you can have but there is a limitation to the number of active connected users you can have. The free pricing tier allows 100 active connections at one time. The more expensive tiers allow for unlimited active connected users. There is no limitation on number of messages. Latency is very low. Changes are displayed almost instantly.
I haven't personally worked with Google cloud messaging or any other real time frameworks so I can't answer that. But firebase has great documentation and is very easy to set up and implement. The only downside is that firebase do not currently provide push notifications. However they can easily be implemented with a push notification service such as Batch