How can I minimize costs for a low‑traffic Azure Cosmos DB Table API workload using the serverless option?
I am designing an application with intermittent, low‑traffic patterns (average‑to‑peak ratio < 10 %) that will store key‑value data in Azure Cosmos DB for Table. To keep expenses predictable and low, I plan to use a serverless account so that I pay only for the request units (RUs) actually consumed and for storage, without any minimum throughput commitmen
datatables