Confused About DocumentDB Pricing

0
votes

I see that in Microsoft Azure Website, pricing for DocumentDB is based on collections. For example, for a 1GB Storage and 100 RU, something about (~£4/mo) is billed for me.

The description is:

At any scale, you can store data and provision throughput capacity. Each collection is billed hourly based on the amount of data stored (in GBs) and throughput reserved in units of 100 RUs/second.

My confusion is this: Is it really billing me for each collection I have? If my application uses a database with 20 collections in it, should I pay (~£80/mo)? Or by collection it means a database?

Thank you all

2
azureazure-cosmosdb
Yes, DocumentDB bills per collection. It helps to think of collections as equivalent to (relational) databases. You provision throughput per collection, run queries against a collection, and store multiple types within a collection. - Aravind Krishna R.

2 Answers

0
votes

Your understanding is correct. You will have to pay for each collection as the throughput is defined per collection. So in your example you'll pay £80 for 20 collections (or £4 per collection).

1
votes

A collection in Document DB can be considered equivalent to a table in normal database terms. It isn't equivalent to a database.