Merge pull request #251153 from seesharprun/rework-mongodb-toc-introduction

Cosmos DB | Rework MongoDB RU/vCore

Author: JamesJBarnett

articles/cosmos-db/.openpublishing.redirection.cosmos-db.json

@@ -6159,6 +6159,11 @@
       "source_path_from_root": "/articles/cosmos-db/nosql/query/geospatial-query.md",
       "redirect_url": "/azure/cosmos-db/nosql/how-to-geospatial-index-query",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/cosmos-db/mongodb/introduction.md",
+      "redirect_url": "/azure/cosmos-db/mongodb/ru/introduction",
+      "redirect_document_id": true
     }
   ]
 }

articles/cosmos-db/mongodb/TOC.yml

@@ -1,15 +1,19 @@
+- name: What is Azure Cosmos DB for MongoDB?
+  href: overview.md
 - name: Choose your model
   href: choose-model.md
 - name: Comparing MongoDB Atlas
   href: cosmos-db-vs-mongodb-atlas.md
-- name: RU-based
+- name: FAQ
+  href: faq.yml
+- name: RU
   items:
-    - name: RU-based MongoDB documentation
+    - name: MongoDB RU documentation
       href: index.yml
     - name: Overview
       items:
-        - name: What is Azure Cosmos DB for MongoDB?
-          href: introduction.md
+        - name: What is Azure Cosmos DB for MongoDB RU?
+          href: ru/introduction.md
         - name: API versions
           items:
             - name: API version 4.2
@@ -40,7 +44,7 @@
           href: quickstart-go.md
     - name: Tutorials
       items:
-        - name: 1 - Create and manage data
+        - name: Create and manage data
           items:
             - name: Node.js console app
               href: nodejs-console-app.md
@@ -60,9 +64,9 @@
                   href: tutorial-develop-nodejs-part-6.md
             - name: Node.js and React app
               href: tutorial-develop-react.md
-        - name: 2 - Query data
+        - name: Query data
           href: tutorial-query.md
-        - name: 3 - Distribute data globally
+        - name: Distribute data globally
           href: tutorial-global-distribution.md
         - name: Aggregation pipeline
           href: tutorial-aggregation.md
@@ -634,5 +638,5 @@
               href: ../use-cases.md
             - name: Social media apps
               href: ../social-media-apps.md
-- name: vCore-based
+- name: vCore
   href: vcore/toc.yml

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

@@ -8,7 +8,7 @@ ms.reviewer: gahllevy
 ms.service: cosmos-db
 ms.subservice: mongodb
 ms.topic: overview
-ms.date: 03/09/2023
+ms.date: 09/12/2023
 ---
 
 # 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
 
 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
+## Choose between RU-based and vCore-based
 
-Here are a few key factors to help you decide which is the right architecture for you:
+Here are a few key factors to help you decide which is the right option 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. |
+### Choose RU-based if
+
+- You're building new cloud-native MongoDB apps or refactoring existing apps for cloud-native benefits.
+- 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.
+- You want limitless horizontal scalability, instantaneous scale up, and granular throughput control.
+- You're running mission-critical applications requiring industry-leading 99.999% availability.
+
+[**Get started with Azure Cosmos DB for MongoDB RU**](./quickstart-python.md)
+
+### Choose vCore-based if
+
+- You're migrating (lift & shift) an existing MongoDB workload or building a new MongoDB application.
+- 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.
+- You prefer high-capacity vertical and horizontal scaling with familiar vCore-based cluster tiers such as M30, M40, M50 and more.
+- You're running applications requiring 99.995% availability.
+
+[**Get started with Azure Cosmos DB for MongoDB vCore**](./vcore/quickstart-portal.md)
+
+> [!TIP]
+> 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.
 
 ## 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:
+The RU and vCore services have different architectures with important billing differences.
+
+### RU-based resources and billing
+
+- You'd like a multi-tenant service that instantly allocates resources to your workload, aligning with storage and throughput requirements.
+
+> [!NOTE]
+> Throughput is based on [Request Units (RUs)](../request-units.md).
+
+- You prefer to pay fixed (standard provisioned throughput) or variable (autoscale) fees corresponding to Request Units (RUs) and consumed storage.
+
+> [!NOTE]
+> RU charges depend on the selected model: provisioned throughput (standard or autoscale) or serverless.
+
+[**Get started with Azure Cosmos DB for MongoDB RU**](./quickstart-python.md)
+
+### vCore-based resources and billing
+
+- You'd like dedicated instances that utilize preset CPU, memory, and storage resources, which can dynamically scale to suit your needs.
+- You prefer to pay a consistent flat fee based on compute (CPU, memory, and the number of nodes) and storage.
 
-| 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. |
+[**Get started with Azure Cosmos DB for MongoDB vCore**](./vcore/quickstart-portal.md)
 
 ## 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).
+> [!div class="nextstepaction"]
+> [Try Azure Cosmos DB for free](../try-free.md)

articles/cosmos-db/mongodb/faq.yml

@@ -0,0 +1,49 @@
+### YamlMime:FAQ
+metadata:
+  title: Frequently asked questions on Azure Cosmos DB for MongoDB
+  description: Get answers to frequently asked questions about Azure Cosmos DB for MongoDB and the differences between the two offers.
+  author: gahl-levy
+  ms.author: gahllevy
+  ms.service: cosmos-db
+  ms.subservice: mongodb
+  ms.topic: faq
+  ms.date: 09/12/2023
+title: Frequently asked questions on Azure Cosmos DB for MongoDB
+summary: |
+  [!INCLUDE[MongoDB](../includes/appliesto-mongodb.md)]
+
+sections:
+  - name: General FAQ
+    questions:
+      - question: |
+          Does Azure Cosmos DB for MongoDB support my data residency requirements?
+        answer: |
+          Yes, data residency is governed at the database account level, which is associated with one or more regions. Typically, you create a database account for each residency requirement. For example, if you have a requirement to store data in the US and EU, you would create two database accounts, one in the US and one in the EU.
+      - question: |
+          Does Azure Cosmos DB for MongoDB support documents larger than 2 MB?
+        answer: |
+          Yes, documents as large as 16 MB are fully supported.
+      - question: |
+          Does Azure Cosmos DB for MongoDB support multi-field sort?
+        answer: |
+          Yes, multi-field sort is supported. A compound index is required for the fields in the sort to ensure the operation is efficient and scalable.
+      - question: |
+          Does Azure Cosmos DB for MongoDB scale linearly?
+        answer: |
+          In many cases, Azure Cosmos DB's costs scale better than linear. For example, if you read a 1-KB document, this operation equates to one Request Unit (RU). But if you read a 10-KB document, this larger operation still equates to roughly one RU. The [capacity calculator](https://cosmos.azure.com/capacitycalculator/) can help you estimate your throughput needs.
+      - question: |
+          How can I encrypt data and manage access at the field level?
+        answer: |
+          Azure Cosmos DB for MongoDB supports Field Level Encryption.
+      - question: |
+          How do I pay for Request Units (RUs)?
+        answer: |
+          Azure Cosmos DB for MongoDB offers three capacity modes: provisioned throughput, autoscale, and serverless. Autoscale instantaneously scales to meet your needs, and serverless only charges for the throughput you use.
+      - question: |
+          Which features are supported in Azure Cosmos DB for MongoDB?
+        answer: |
+          Azure Cosmos DB for MongoDB supports a rich set of MongoDB features backed by Azure Cosmos DB's limitless scale architecture. These features include: Aggregation pipelines, Change streams, Indexes, Geospatial queries, and more. For more information, see [feature support matrix](feature-support-42.md). Not sure if your workload is ready?
+      - question: |
+          Does Azure Cosmos DB for MongoDB run on-premises?
+        answer: |
+          Azure Cosmos DB for MongoDB is a cloud-native multi-tenant service and isn't available on-premises. Azure Cosmos DB offers an [emulator for local development and testing](../emulator.md).