6 documented Azure Cosmos DB cost inefficiencies, each with how to detect it and how to fix it.
Azure Cosmos DBCER-0142
Azure Cosmos DB is optimized for low-latency, globally distributed workloads - not long-term storage of infrequently accessed data. Yet in many environments, cold data such as logs, telemetry, or historical records is retained in Cosmos DB...
Azure Cosmos DBCER-0438
Containers and databases created for load tests, migrations, retired features, proofs of concept or one-off data loads often keep their provisioned throughput long after traffic stops. Provisioned RU/s is reserved capacity: it is billed...
Azure Cosmos DBCER-0439
Cosmos DB provisioned throughput comes in two modes. Standard (manual) throughput bills the RU/s you set every hour regardless of use. Autoscale lets the system scale between 10% and 100% of a maximum (Tmax) and bills the highest RU/s...
Azure Cosmos DBCER-0440
Production Cosmos DB accounts usually carry a stable floor of provisioned throughput that runs every hour of the year: core containers on manual RU/s, the 10% minimum of autoscale containers, and the same throughput repeated in every...
Azure Cosmos DBCER-0441
Cosmos DB makes global replication a checkbox: regions can be added to an account at any time, and every container's provisioned throughput and every GB of data is then reserved and stored again in each region. An account with two extra...
Azure Cosmos DBCER-0442
Cosmos DB accounts in periodic backup mode take a full backup at a fixed interval (every 4 hours by default) and keep the latest two copies by default. Two copies are free; every copy beyond two is billed as backup storage for the full...
