Skip to content

Commit b980cc9

Browse files
committed
Rework choose model
1 parent a325849 commit b980cc9

File tree

1 file changed

+46
-16
lines changed

1 file changed

+46
-16
lines changed

articles/cosmos-db/mongodb/choose-model.md

Lines changed: 46 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.reviewer: gahllevy
88
ms.service: cosmos-db
99
ms.subservice: mongodb
1010
ms.topic: overview
11-
ms.date: 03/09/2023
11+
ms.date: 09/12/2023
1212
---
1313

1414
# What is RU-based and vCore-based Azure Cosmos DB for MongoDB?
@@ -17,27 +17,57 @@ Azure Cosmos DB is a fully managed NoSQL and relational database for modern app
1717

1818
Both, the Request Unit (RU) and vCore-based Azure Cosmos DB for MongoDB offering make it easy to use Azure Cosmos DB as if it were a MongoDB database. Both options work without the overhead of complex management and scaling approaches. You can use your existing MongoDB skills and continue to use your favorite MongoDB drivers, SDKs, and tools by pointing your application to the connection string for your account using the API for MongoDB. Additionally, both are cloud-native offerings that can be integrated seamlessly with other Azure services to build enterprise-grade modern applications.
1919

20-
## Choosing between RU-based and vCore-based options
20+
## Choose between RU-based and vCore-based
2121

22-
Here are a few key factors to help you decide which is the right architecture for you:
22+
Here are a few key factors to help you decide which is the right option for you.
2323

24-
| Factor | RU-based | vCore-based |
25-
| ----------- | ----------- | -------|
26-
| What do you want to do | • Works well if you're trying to build new cloud-native MongoDB apps or refactor existing apps for all the benefits of a cloud-native offering | • Works well if you're trying to lift and shift existing MongoDB apps and run them as-is on a fully supported managed service. |
27-
| What are your availability needs | • Offers upto [99.999%](../high-availability.md#slas) of availability with multi-region deployments | • Offers competitive SLA (once generally available) |
28-
| How do you want to scale | • Offers limitless horizontal scalability, instantaneous scale up and granular throughput control. | • Offers high-capacity vertical and horizontal scaling with familiar vCore-based cluster tier options to choose from. |
29-
| What are your top read & query patterns | • Works well for workloads with more point reads *(fetching a single item by its ID and shard key value)* and lesser long running queries and complex aggregation pipeline operations. | • Works irrespective of the operation types in your workload. Operations may include workloads with long-running queries, complex aggregation pipelines, distributed transactions, joins, etc. |
24+
### Choose RU-based if
25+
26+
- You're building new cloud-native MongoDB apps or refactoring existing apps for cloud-native benefits.
27+
- Your workload has more point reads (fetching a single item by its _id and shard key value) and few long-running queries and complex aggregation pipeline operations.
28+
- You want limitless horizontal scalability, instantaneous scale up, and granular throughput control.
29+
- You're running mission-critical applications requiring industry-leading 99.999% availability.
30+
31+
[**Get started with Azure Cosmos DB for MongoDB RU**](./quickstart-python.md)
32+
33+
### Choose vCore-based if
34+
35+
- You're migrating (lift & shift) an existing MongoDB workload or building a new MongoDB application.
36+
- Your workload has more point reads (fetching a single item by its ID and shard key value) and few long-running queries and complex aggregation pipeline operations.
37+
- You prefer high-capacity vertical and horizontal scaling with familiar vCore-based cluster tiers such as M30, M40, M50 and more.
38+
- You're running applications requiring 99.995% availability.
39+
40+
[**Get started with Azure Cosmos DB for MongoDB vCore**](./vcore/quickstart-portal.md)
41+
42+
> [!TIP]
43+
> Want to try the Azure Cosmos DB for MongoDB with no commitment? Create an Azure Cosmos DB account using [Try Azure Cosmos DB](../try-free.md) for free.
3044
3145
## Resource and billing differences between the options
3246

33-
There are differences between the offerings in the way the resources are assigned and billed on the platform:
47+
The RU and vCore services have different architectures with important billing differences.
48+
49+
### RU-based resources and billing
50+
51+
- You'd like a multi-tenant service that instantly allocates resources to your workload, aligning with storage and throughput requirements.
52+
53+
> [!NOTE]
54+
> Throughput is based on [Request Units (RUs)](../request-units.md).
55+
56+
- You prefer to pay fixed (standard provisioned throughput) or variable (autoscale) fees corresponding to Request Units (RUs) and consumed storage.
57+
58+
> [!NOTE]
59+
> RU charges depend on the selected model: provisioned throughput (standard or autoscale) or serverless.
60+
61+
[**Get started with Azure Cosmos DB for MongoDB RU**](./quickstart-python.md)
62+
63+
### vCore-based resources and billing
64+
65+
- You'd like dedicated instances that utilize preset CPU, memory, and storage resources, which can dynamically scale to suit your needs.
66+
- You prefer to pay a consistent flat fee based on compute (CPU, memory, and the number of nodes) and storage.
3467

35-
| Resource details | RU-based | vCore-based |
36-
| ----------- | ----------- | -------|
37-
| How are the resources assigned | &bull; This option is a multi-tenant service that instantly assigns resources to the workload to meet its storage and throughput needs. <br/>&bull; Throughput uses the concept of [Request Units (RUs)](../request-units.md). | &bull; This option provides dedicated instances using preset CPU, memory and storage resources that scale to meet your needs. |
38-
| How are the resources billed | &bull; You pay variable fees for the RUs and consumed storage. <br/>&bull; RU charges are based on the choice of the model: provisioned throughput (standard or autoscale) or serverless. | &bull; You pay consistent flat fee based on the compute (CPU, memory and the number of nodes) and storage. |
68+
[**Get started with Azure Cosmos DB for MongoDB vCore**](./vcore/quickstart-portal.md)
3969

4070
## Next steps
4171

42-
- [Create a Go app](quickstart-go.md) using Azure Cosmos DB for MongoDB.
43-
- Deploy Azure Cosmos DB for MongoDB vCore [using a Bicep template](vcore/quickstart-bicep.md).
72+
> [!div class="nextstepaction"]
73+
> [Try Azure Cosmos DB for free](../try-free.md)

0 commit comments

Comments
 (0)