You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/serverless.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ The Azure Cosmos DB serverless offering lets you use your Azure Cosmos DB accoun
21
21
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:
22
22
23
23
- 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.
25
25
26
26
## Use-cases
27
27
@@ -48,6 +48,7 @@ Any container that is created in a serverless account is a serverless container.
48
48
- You can't read or update the throughput on a serverless container and doing so returns an error.
49
49
- You can't create a shared throughput database in a serverless account and doing so returns an error.
50
50
- 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.
51
52
52
53
### Serverless 1 TB container preview
53
54
@@ -80,4 +81,4 @@ Get started with serverless with the following articles:
80
81
-[Azure Cosmos DB Serverless 1-TB container](serverless-1TB.md)
81
82
-[Request Units in Azure Cosmos DB](request-units.md)
82
83
-[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