rnehme

4 ms·

1. 1.▲
   by rnehme 7y ago

   Hi, I am from Cosmos DB engineering team. 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 m
2. 2.▲
   by rnehme 7y ago

   Hi, I am from Cosmos DB engineering team. 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 Mongo
3. 3.▲
   by rnehme 7y ago

   Hi, I am from Azure Cosmos DB Engineering Team. The TLA+ specs are fairly up to date. Thanks.
4. 4.▲
   by rnehme 7y ago

   Hi, I am from Azure Cosmos DB Engineering Team. @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 provisione
5. 5.▲
   by rnehme 7y ago

   Hi, I am from Azure Cosmos DB Engineering Team. 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/cosm
6. 6.▲
   by rnehme 7y ago

   Hi, I am from Azure Cosmos DB Engineering Team. 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.
7. 7.▲
   by rnehme 7y ago

   Hi, I am from Azure Cosmos DB Engineering Team. Please feel free to send us the details of your workload that suffered from poor performance to AskCosmosDB@microsoft.com (it is a direct way to reach the engineering team and it does not cost