Stats
Actions
Tags
From documentdb
Guides storage configuration for Azure DocumentDB clusters: choosing Premium SSD v2 vs v1, IOPS/bandwidth caps by compute tier, CMK trade-offs, migration paths, and disk-hydration sequencing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/documentdb:storageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Azure DocumentDB clusters use **remote premium SSD storage**. Two disk types are offered:
Azure DocumentDB clusters use remote premium SSD storage. Two disk types are offered:
| Storage type | IOPS / bandwidth scaling | Max IOPS | CMK | Use it for |
|---|---|---|---|---|
| Premium SSD (v1) | Scales with disk capacity — bigger disk → higher IOPS | 20,000 | ✔️ | Legacy clusters, scenarios that require CMK |
| Premium SSD v2 | Decoupled from disk size — IOPS/bandwidth gated by compute tier | 80,000 | ❌ | New production clusters; any I/O-intensive workload |
Premium SSD v2 is the default recommendation for new clusters. It delivers up to a 12× performance boost at no added cost by removing the disk-size lever from the IOPS equation — you size storage for capacity and size compute for throughput, independently.
On Premium SSD v1, hitting 20,000 IOPS required provisioning a 20 TB disk even when only ~1 TB of data was stored. On Premium SSD v2, the highest achievable IOPS and bandwidth for the chosen compute tier are auto-configured regardless of disk size:
npx claudepluginhub azure/documentdb-agent-kit --plugin documentdbProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.