Question

A gaming company stores telemetry in a Cosmos DB container partitioned by /gameId. One extremely popular game generates over 40 GB of telemetry for its single gameId value, and writes for that game are now failing. The team wants to keep gameId as the primary way to group data while resolving the storage ceiling. Which redesign best addresses the problem?

Accepted Answer

Recreate the container with a hierarchical partition key of /gameId then /sessionId, distributing each game's data across many logical partitions.

Answer

Increase the provisioned throughput (RU/s) on the container so the large partition can accept more writes.

Answer

Enable autoscale on the container to automatically expand the storage limit of the logical partition.

Answer

Switch the account to serverless mode, which removes the 20 GB per-logical-partition storage limit.