Architecting for Physical Partition Splitting Latency in High-Throughput Write Workloads

Partition splitting occurs when a physical partition hits 50GB or its RU limit. Architecture must account for the 50/50 throughput split to avoid temporary 'hot' child partitions.

In Azure Cosmos DB, physical partitions are the units of scalability. When a partition reaches its storage (50GB) or throughput limit, it splits into two child partitions. The critical architectural nuance is that the provisioned RUs are split exactly 50/50 between the new partitions. If your data distribution is skewed, one child partition may immediately become a 'hot' partition, leading to 429 Throttle errors even if the total container RUs are under-utilized. High-throughput systems must use synthetic keys or hierarchical partitioning to ensure even distribution post-split.