Azure Cosmos DB is part of the serverless services available in Azure. This means that the chances of configuring and provisioning servers to run it are either maximally limited or not available. As you probably noticed, we were not able to define how many instances of a service we would like to run (or nodes or clusters). Instead, we have to define throughput for each collection individually:
A simple calculator display also estimates the costs of a collection per hour and day. The unit of throughput in Azure Cosmos DB is request units (RUs). During the creation of a container (or a collection—you can use both definitions), ...
