rnehme
Thank you for the feedback!
We have published a number of documents on pricing transparency and cost optimization of your Cosmos DB cost that we want to make sure everyone is aware of:
[1] Pricing model - https://docs.microsoft.com/en-us/azure/cosmos-db/how-pricing...
[2] Optimize cost for your dev/test workloads - https://docs.microsoft.com/en-us/azure/cosmos-db/optimize-de...
[3] Total Cost of Ownership (TCO) - https://docs.microsoft.com/en-us/azure/cosmos-db/total-cost-...
[4] Understand your bill - https://docs.microsoft.com/en-us/azure/cosmos-db/understand-...
[5] Optimize provisioned throughput cost - https://docs.microsoft.com/en-us/azure/cosmos-db/optimize-co...
[6] Optimize query cost - https://docs.microsoft.com/en-us/azure/cosmos-db/optimize-co...
[7] Optimize storage cost - https://docs.microsoft.com/en-us/azure/cosmos-db/optimize-co...
[8] Optimize reads and writes cost - https://docs.microsoft.com/en-us/azure/cosmos-db/optimize-co...
[9] Optimize multi-regions cost - https://docs.microsoft.com/en-us/azure/cosmos-db/optimize-co...
[10] Optimize with reserved capacity - https://docs.microsoft.com/en-us/azure/cosmos-db/cosmos-db-r...
If you have any questions regarding pricing, please feel free to reach out to us directly at [email protected] (direct line to the product team).
We do really appreciate the feedback.
Thank you.
Yes, for shared throughput database, you will need to create a new database.
- You can create MongoDB API collections with shard keys defined. It is fully supported by MongoDB driver
- Support MongoDB collections without shard key specified is coming in May
Thank you for the feedback on the docs and the missing code samples. We will add those in the docs.
Thanks!
The TLA+ specs are fairly up to date.
Thanks.
@llcoolv has responded and the response is correct.
For scenarios where you create a lot of collections/tables, we recommend to provision throughput on a database and share the provisioned throughput among all the containers – to save on costs. You can change the throughput at database exactly like how you will change the throughput at container level. It is the same API, it is supported via CLI, SDK, Rest API and Portal as well.
The entry point for database level throughout is 400RUs $24 per month and you can add any number of collections/tables that can share this throughput. You can scale up and down in the increments of 100RUs (or $6/month).
Please see the following links for details:
[1] https://docs.microsoft.com/en-us/azure/cosmos-db/set-through...
[2] https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-prov...
[3] https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-prov...
Please see the sample here for moving data:
[4] https://github.com/Azure/azure-documentdb-dotnet/tree/master...
Thanks!
For development (before going into production) with Azure Cosmos DB, we suggest a number of options (also documented here: https://docs.microsoft.com/en-us/azure/cosmos-db/optimize-de...):
[1] Cosmos DB emulator (Cosmos DB Local version) - https://docs.microsoft.com/en-us/azure/cosmos-db/local-emula.... The Azure Cosmos DB Emulator provides a local environment that emulates the Azure Cosmos DB service for development purposes. Using the Azure Cosmos DB Emulator, you can develop and test your application locally, without creating an Azure subscription or incurring any costs. When you're satisfied with how your application is working in the Azure Cosmos DB Emulator, you can switch to using an Azure Cosmos DB account in the cloud. Support for Cosmos DB emulator on Linux is coming.
[2] We provide Try Cosmos DB for free experience - https://azure.microsoft.com/try/cosmosdb/. There is Try Azure Cosmos DB for free experience which gives you a time-limited full-service experience with Azure Cosmos DB. It is designed for trying out Cosmos DB, doing a tutorial, a demo, doing a quick start, a lab without requiring an Azure account or a credit card.
[3] We provide a free tier (Cosmos DB is a part of free account) - https://azure.microsoft.com/free. In Azure, we support a free tier with 12 month access to all popular services in Azure. As a part of free tier specifically for Cosmos DB you get 5GB in storage and 400RUs.
Thanks so much!
We are in the process of updating the Azure pricing calculator to provide various options (e.g., # of regions, single vs. multi-master, etc.). The updates to the calculator are coming shortly.
In the meantime, please feel free to ping us at [email protected], if you need any help with cost estimates or have any questions.
Please feel free to send us the details of your workload that suffered from poor performance to [email protected] (it is a direct way to reach the engineering team and it does not cost anything), and we can help determine why and provide with the recommendations.
For best practices and performance optimizations, the following links will help:
https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-que...
https://docs.microsoft.com/en-us/azure/cosmos-db/performance...
https://docs.microsoft.com/en-us/azure/cosmos-db/performance...
https://docs.microsoft.com/en-us/azure/cosmos-db/performance...
Also, the following conceptual docs will help:
https://docs.microsoft.com/en-us/azure/cosmos-db/partitionin...
https://docs.microsoft.com/en-us/azure/cosmos-db/partition-d...
https://docs.microsoft.com/en-us/azure/cosmos-db/request-uni...
We are doing a full refresh of our docs (rewriting a lot of the older content and adding new technical content). We welcome feedback on how we can make the docs better and invite everyone to contribute via public PR/Github. If there are any topics that are missing in our docs or are not easily discoverable, please let us know. We will make sure to address it.
We are committed to building a great community. As a relatively young database, we have ton of work ahead, but we are super committed to making sure we make developers successful.