# 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).

- Skill: `atc-net/cosmosdb-throughput` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add atc-net/cosmosdb-throughput`
- Raw SKILL.md: https://api.skillmd.com/api/skills/atc-net/cosmosdb-throughput/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: atc-net (https://skillmd.com/u/atc-net)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/atc-net/cosmosdb-throughput

---


# 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](references/throughput-autoscale.md) - Use autoscale for variable workloads
- [throughput-right-size](references/throughput-right-size.md) - Right-size provisioned throughput
- [throughput-serverless](references/throughput-serverless.md) - Consider serverless for dev/test
- [throughput-burst](references/throughput-burst.md) - Understand burst capacity
- [throughput-container-vs-database](references/throughput-container-vs-database.md) - Choose allocation level wisely