Azure 文档数据库集合可以有多少个分区？
How many partitions Azure Document DB collection can have?
我打算创建一个分区集合。我正在努力为收集确定正确的分区键。
但是，我不确定分区集合可以有多少个分区？有没有限制？
分区数没有硬性限制。文档数据库定位为无限可扩展。
您的分区键应该足够多样化，这样单个分区键就不必存储太多数据（每个分区 10 GB 似乎是限制）并匹配您的查询模式。
正如官方文档所述Single partition and partitioned collections：
Partitioned collections can span multiple partitions and support unlimited storage and throughput. You must specify a partition key for the collection.
The number of partitions is determined by DocumentDB based on the storage size and the provisioned throughput of the collection. Every partition in DocumentDB has a fixed amount of SSD-backed storage associated with it, and is replicated for high availability. Partition management is fully managed by Azure DocumentDB, and you do not have to write complex code or manage your partitions. DocumentDB collections are practically unlimited in terms of storage and throughput.
为了识别正确的集合分区键，我建议您可以参考Designing for partitioning。
我打算创建一个分区集合。我正在努力为收集确定正确的分区键。
但是，我不确定分区集合可以有多少个分区？有没有限制？
分区数没有硬性限制。文档数据库定位为无限可扩展。
您的分区键应该足够多样化，这样单个分区键就不必存储太多数据（每个分区 10 GB 似乎是限制）并匹配您的查询模式。
正如官方文档所述Single partition and partitioned collections：
Partitioned collections can span multiple partitions and support unlimited storage and throughput. You must specify a partition key for the collection.
The number of partitions is determined by DocumentDB based on the storage size and the provisioned throughput of the collection. Every partition in DocumentDB has a fixed amount of SSD-backed storage associated with it, and is replicated for high availability. Partition management is fully managed by Azure DocumentDB, and you do not have to write complex code or manage your partitions. DocumentDB collections are practically unlimited in terms of storage and throughput.
为了识别正确的集合分区键，我建议您可以参考Designing for partitioning。