Azure Cosmos DB - Partitioning

In Azure Cosmos DB, you can store and query schema-less data with order-of-millisecond response times at any scale. Azure Cosmos DB provides containers for storing data called collections (for documents), graphs, or tables.

Containers are logical resources and can span one or more physical partitions or servers. The number of partitions is determined by Azure Cosmos DB based on the storage size and the provisioned throughput of the container.

A physical partition is a fixed amount of reserved SSD-backed storage. Each physical partition is replicated for high availability. One or more physical partitions make up a container. Physical partition management is fully managed by Azure Cosmos DB, and you don't have to write complex code or manage your partitions. Azure Cosmos DB containers are unlimited in terms of storage and throughput. #azurecosmosdb #azure #nosql #cloud

[jimifriis]

at 10:20 - good insight to have "Fan-out operations on a ~1GB collection will not be more heavy than a non fan-out"
Thanks for a short and yet explanatory session!

[adamreed]

I've read of a 10GB Limit on Partitions, per-key (ex. : "Errors":["Partition key reached maximum size of 10 GB"]), this video does not describe any such limitations, can you elaborate?

[garreyxu]

Thanks for the great video. Could I ask for an example of how the ratio of INSERTs vs UPDATEs affects Cosmos DB object modeling? Thanks in advanc!

[karmadipdodiya]

What would be a good partition key for Telematics IOT Data. (Device sending GPS, Acceleration, Gyroscope, Events, ETC..) You can consider Per second you received 1 GPS data from one device.
What API I have to choose for it in Cosmos DB? Cassandra or Document?

[Ruslan-S]

A very helpful explanation, thank you! Now I'm wondering how would I convert a fixed-storage container into a partitioned one. Seems like I need to create a new Container and copy all items from my old one to it.

[srinathharidas]

Hello, Can we use multiple keys for a partition?