Skip to content

Commit 06c100f

Browse files
committed
Merge branch 'patch-1' of https://github.com/vgarmash/azure-docs into cosmos-serverless-note
2 parents 6c595ee + 465c820 commit 06c100f

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/cosmos-db/serverless.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ The Azure Cosmos DB serverless offering lets you use your Azure Cosmos DB accoun
2121
Every database operation in Azure Cosmos DB has a cost expressed in [Request Units (RUs)](request-units.md). How you're charged for this cost depends on the type of Azure Cosmos DB account you're using:
2222

2323
- In [provisioned throughput](set-throughput.md) mode, you have to commit to a certain amount of throughput (expressed in Request Units per second or RU/s) that is provisioned on your databases and containers. The cost of your database operations is then deducted from the number of Request Units available every second. At the end of your billing period, you get billed for the amount of throughput you've provisioned.
24-
- In serverless mode, you don't have to configure provisioned throughput when creating containers in your Azure Cosmos DB account. At the end of your billing period, you get billed for the number of Request Units that were consumed by your database operations.
24+
- In serverless mode, you don't have to configure provisioned throughput when creating containers in your Azure Cosmos DB account. Serverless containers can currently deliver a maximum throughput of 5,000 RU/s and it can't be changed by user. At the end of your billing period, you get billed for the number of Request Units that were consumed by your database operations.
2525

2626
## Use-cases
2727

@@ -48,6 +48,7 @@ Any container that is created in a serverless account is a serverless container.
4848
- You can't read or update the throughput on a serverless container and doing so returns an error.
4949
- You can't create a shared throughput database in a serverless account and doing so returns an error.
5050
- Serverless containers can store a maximum of 50 GB of data and indexes.
51+
- Serverless container do not offer unlimited throughput. Serverless containers can currently deliver a maximum throughput of 5,000 RU/s. If you need higher throuput numbers please choose provisioned capacity mode. See [Azure Cosmos DB service quotas](concepts-limits.md) for details.
5152

5253
### Serverless 1 TB container preview
5354

@@ -80,4 +81,4 @@ Get started with serverless with the following articles:
8081
- [Azure Cosmos DB Serverless 1-TB container](serverless-1TB.md)
8182
- [Request Units in Azure Cosmos DB](request-units.md)
8283
- [Choose between provisioned throughput and serverless](throughput-serverless.md)
83-
- [Pricing model in Azure Cosmos DB](how-pricing-works.md)
84+
- [Pricing model in Azure Cosmos DB](how-pricing-works.md)

0 commit comments

Comments
 (0)