An ice-road convoy tracker starts receiving HTTP 429 responses from…

Question

An ice-road convoy tracker starts receiving HTTP 429 responses from Cosmos DB after a teammate replaced point reads with broad SELECT scans. What should the developer recognize as Cosmos throughput currency, and what should they prefer?

Accepted Answer

Request units (RUs) measure operation cost—prefer cheaper point reads over expensive unrestricted scans when the key is known — Cosmos charges in request units—think tokens at the arcade. Point reads are a cheap game; SELECT scans burn the roll and earn you 429s when the key was already in your pocket.

Answer

Virtual machine vCPU counts are the Cosmos billing unit; add more App Service instances only

Answer

Blob Storage ingress gigabytes throttle Cosmos; move all documents into Azure Files

Answer

Azure Front Door cache hit ratio is the Cosmos throughput limit; disable CDN

An ice-road convoy tracker starts receiving HTTP 429 responses from Cosmos DB after a teammate replaced point reads with broad `SELECT *` scans. What should the developer recognize as Cosmos throughput currency, and what should they prefer?

Short Explanation

Full Explanation

An ice-road convoy tracker starts receiving HTTP 429 responses from Cosmos DB after a teammate replaced point reads with broad SELECT * scans. What should the developer recognize as Cosmos throughput currency, and what should they prefer?

Short Explanation

Full Explanation

An ice-road convoy tracker starts receiving HTTP 429 responses from Cosmos DB after a teammate replaced point reads with broad `SELECT *` scans. What should the developer recognize as Cosmos throughput currency, and what should they prefer?