Merge pull request #231888 from MicrosoftDocs/release-cosmos-mongo-api

Release cosmos mongo api--scheduled release at 10 am of 3/24

Author: huypub

.openpublishing.publish.config.json

@@ -542,6 +542,12 @@
       "branch": "main",
       "branch_mapping": {}
     },
+    {
+      "path_to_root": "azure-cosmos-db-mongodb-mern-web-app",
+      "url": "https://github.com/Azure-samples/msdocs-azure-cosmos-db-mongodb-mern-web-app/",
+      "branch": "main",
+      "branch_mapping": {}
+    },
     {
       "path_to_root": "azure-cosmos-spark",
       "url": "https://github.com/Azure/azure-cosmosdb-spark",

articles/cosmos-db/includes/appliesto-mongodb-vcore.md

@@ -0,0 +1,12 @@
+---
+author: seesharprun
+ms.author: sidandrews
+ms.reviewer: mjbrown
+ms.service: cosmos-db
+ms.topic: include
+ms.date: 03/07/2023
+---
+
+APPLIES TO:
+:::image type="icon" source="media/applies-to/yes-icon.svg" border="false":::
+MongoDB vCore

articles/cosmos-db/mongodb/TOC.yml

@@ -0,0 +1,43 @@
+---
+title: Choose between RU-based and vCore-based models
+titleSuffix: Azure Cosmos DB for MongoDB
+description: Choose whether the RU-based or vCore-based option for Azure Cosmos DB for MongoDB is ideal for your workload.
+author: nayakshweta
+ms.author: shwetn
+ms.reviewer: gahllevy
+ms.service: cosmos-db
+ms.subservice: mongodb
+ms.topic: overview
+ms.date: 03/09/2023
+---
+
+# What is RU-based and vCore-based Azure Cosmos DB for MongoDB?
+
+Azure Cosmos DB is a fully managed NoSQL and relational database for modern app development.
+
+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.
+
+## Choosing between RU-based and vCore-based options
+
+Here are a few key factors to help you decide which is the right architecture for you:
+
+| Factor | RU-based | vCore-based |
+| ----------- | ----------- | -------|
+| 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. |
+| 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) |
+| 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. |
+| 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. |
+
+## Resource and billing differences between the options
+
+There are differences between the offerings in the way the resources are assigned and billed on the platform:
+
+| Resource details | RU-based | vCore-based |
+| ----------- | ----------- | -------|
+| 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. |
+| 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. |
+
+## Next steps
+
+- [Create a Go app](quickstart-go.md) using Azure Cosmos DB for MongoDB.
+- Deploy Azure Cosmos DB for MongoDB vCore [using a Bicep template](vcore/quickstart-bicep.md).

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

@@ -0,0 +1,34 @@
+- name: vCore-based MongoDB documentation
+  href: index.yml
+- name: Overview
+  items:
+    - name: What is vCore-based Azure Cosmos DB for MongoDB?
+      href: introduction.md
+- name: Quickstarts
+  items:
+    - name: Create resources - Azure portal
+      href: quickstart-portal.md
+    - name: Create resources - Bicep template
+      href: quickstart-bicep.md
+- name: Tutorials
+  items:
+    - name: Build web applications
+      items:
+        - name: Node.js
+          href: tutorial-nodejs-web-app.md
+- name: Concepts
+  items:
+    - name: MongoDB feature support
+      href: compatibility.md
+    - name: High availability
+      href: high-availability.md
+    - name: Migration options
+      href: migration-options.md
+    - name: Security
+      href: security.md
+- name: How to
+  items:
+    - name: Scale cluster
+      href: how-to-scale-cluster.md
+    - name: Restore cluster
+      href: how-to-restore-cluster.md