Documentdb | Pricing ~upd~

: You are typically charged per million I/O requests.

If you’ve been in the cloud database space for a while, you remember —Microsoft’s original NoSQL database service. Today, DocumentDB is the core of Azure Cosmos DB , a globally distributed, multi-model database service. But one thing hasn’t changed: pricing can be confusing. documentdb pricing

The first and often most significant cost driver is the . DocumentDB employs a distributed, storage-compute architecture. Users do not pay for a single "database server" but rather for the instances that perform the compute work. Pricing here is determined by the instance class selected (e.g., db.r5 or db.t3 classes) and the region in which the cluster is deployed. Because DocumentDB separates compute from storage, users can scale the number of instances up or down independently of the data size. A primary instance handles write operations, while up to 15 replica instances can be added to handle read traffic. Consequently, the compute cost scales linearly with the number of replicas added to achieve desired performance throughput. : You are typically charged per million I/O requests