Cosmosdb Throughput

Azure Cosmos DB throughput and scaling best practices: autoscale for variable workloads, right-sizing provisioned throughput, serverless for dev/test, burst capacity, and container vs database throughput allocation. USE FOR: Cosmos DB autoscale, provisioned throughput, serverless, burst capacity, RU/s sizing, container throughput, database throughput, cost optimization, over-provisioning, under-provisioning, throttling prevention. DO NOT USE FOR: RU consumption monitoring (use cosmosdb-monitoring), partition key design (use cosmosdb-partition-key).

atc-net Updated 3 repo stars

File contents

Azure Cosmos DB Throughput & Scaling

Best practices for provisioning and managing throughput in Azure Cosmos DB.

When to Apply

Reference these guidelines when:

  • Choosing between autoscale and provisioned throughput
  • Right-sizing RU/s for workloads
  • Evaluating serverless vs provisioned
  • Setting up container vs database level throughput

Rules

  • throughput-autoscale - Use autoscale for variable workloads
  • throughput-right-size - Right-size provisioned throughput
  • throughput-serverless - Consider serverless for dev/test
  • throughput-burst - Understand burst capacity
  • throughput-container-vs-database - Choose allocation level wisely

atc-net/atc-agentic-toolkit/tree/main/plugins/cosmosdb/skills/cosmosdb-throughput commit 3e59e2313c

Frequently asked questions

npx skillmds@latest add atc-net/cosmosdb-throughput