|
1 | 1 | ### YamlMime:FAQ |
2 | 2 | metadata: |
3 | | - title: "Frequently asked questions about the Azure Cosmos DB's API for MongoDB" |
4 | | - description: "Get answers to Frequently asked questions about the Azure Cosmos DB's API for MongoDB" |
| 3 | + title: Frequently asked questions |
| 4 | + titleSuffix: Azure Cosmos DB for MongoDB vCore |
| 5 | + description: Get answers to frequently asked questions about Azure Cosmos DB for MongoDB vCore. |
5 | 6 | author: seesharprun |
6 | 7 | ms.author: sidandrews |
7 | | - ms.reviewer: gahllevy |
| 8 | + ms.reviewer: mjbrown |
8 | 9 | ms.service: cosmos-db |
9 | | - ms.subservice: mongodb |
| 10 | + ms.subservice: nosql |
10 | 11 | ms.topic: faq |
11 | | - ms.date: 04/28/2020 |
12 | | -title: "Frequently asked questions about the Azure Cosmos DB's API for MongoDB" |
| 12 | + ms.date: 02/22/2024 |
| 13 | +title: Frequently asked questions about Azure Cosmos DB for MongoDB vCore |
13 | 14 | summary: | |
14 | | - [!INCLUDE[MongoDB](../includes/appliesto-mongodb.md)] |
15 | | - |
16 | | - The Azure Cosmos DB's API for MongoDB is a wire-protocol compatibility layer that allows applications to easily and transparently communicate with the native Azure Cosmos DB database engine by using existing, community-supported SDKs and drivers for MongoDB. Developers can now use existing MongoDB toolchains and skills to build applications that take advantage of Azure Cosmos DB. Developers benefit from the unique capabilities of Azure Cosmos DB, which include global distribution with multi-region write replication, auto-indexing, backup maintenance, financially backed service level agreements (SLAs) etc. |
17 | | -
|
| 15 | + [!INCLUDE[MongoDB vCore](../../includes/appliesto-mongodb-vcore.md)] |
18 | 16 | sections: |
19 | 17 | - name: General |
20 | 18 | questions: |
21 | 19 | - question: | |
22 | | - How do I connect to my database? |
| 20 | + What options does Azure Cosmos DB offer for MongoDB users? |
23 | 21 | answer: | |
24 | | - The quickest way to connect to an Azure Cosmos DB database with Azure Cosmos DB's API for MongoDB is to head over to the [Azure portal](https://portal.azure.com). Go to your account and then, on the left navigation menu, click **Quick Start**. Quickstart is the best way to get code snippets to connect to your database. |
25 | | - |
26 | | - Azure Cosmos DB enforces strict security requirements and standards. Azure Cosmos DB accounts require authentication and secure communication via TLS, so be sure to use TLSv1.2. |
27 | | - |
28 | | - For more information, see [Connect to your Azure Cosmos DB database with Azure Cosmos DB's API for MongoDB](connect-account.md). |
29 | | - |
| 22 | + Azure Cosmos DB is a fully managed NoSQL and relational database for modern app development. |
| 23 | +
|
| 24 | + 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. |
30 | 25 | - question: | |
31 | | - Error codes while using Azure Cosmos DB's API for MongoDB? |
| 26 | + How do I choose between Azure Cosmos DB for MongoDB RU and Azure Cosmos DB for MongoDB vCore? |
32 | 27 | answer: | |
33 | | - Along with the common MongoDB error codes, the Azure Cosmos DB's API for MongoDB has its own specific error codes. These can be found in the [Troubleshooting Guide](error-codes-solutions.md). |
34 | | - |
| 28 | + Here are a few key factors to help you decide between the two options. |
| 29 | +
|
| 30 | + - Choose RU-based if: |
| 31 | + - You're building new cloud-native MongoDB apps or refactoring existing apps for cloud-native benefits. |
| 32 | + - 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. |
| 33 | + - You want limitless horizontal scalability, instantaneous scale up, and granular throughput control. |
| 34 | + - You're running mission-critical applications requiring industry-leading 99.999% availability. |
| 35 | + - Choose vCore-based if: |
| 36 | + - You're migrating (lift & shift) an existing MongoDB workload or building a new MongoDB application. |
| 37 | + - Your workload has more long-running queries, complex aggregation pipelines, distributed transactions, joins, etc. |
| 38 | + - You prefer high-capacity vertical and horizontal scaling with familiar vCore-based cluster tiers such as M30, M40, M50, and more. |
| 39 | + - You're running applications requiring 99.995% availability. |
| 40 | + - You need native support for storing and searching vector embeddings. |
35 | 41 | - question: | |
36 | | - Is the Simba driver for MongoDB supported for use with Azure Cosmos DB's API for MongoDB? |
| 42 | + Are there billing differences between Azure Cosmos DB for MongoDB RU and Azure Cosmos DB for MongoDB vCore? |
37 | 43 | answer: | |
38 | | - Yes, you can use Simba's Mongo ODBC driver with Azure Cosmos DB's API for MongoDB |
| 44 | + The RU and vCore services have different architectures with important billing differences. |
39 | 45 |
|
| 46 | + The RU service variant is a multitenant service that instantly allocates resources to your workload, aligning with storage and throughput requirements. Throughput for this service is based on [request units](../../request-units.md). This service is optimized for users who prefer to pay fixed (standard provisioned throughput) or variable (autoscale) fees corresponding to Request Units (RUs) and consumed storage. Actual RU charges depend on the selected model: provisioned throughput (standard or autoscale) or serverless. |
| 47 | +
|
| 48 | + The vCore service variant creates dedicated instances that utilize preset CPU, memory, and storage resources, which can dynamically scale to suit your needs. This service is optimized for users who prefer to pay a consistent flat fee based on compute (CPU, memory, and the number of nodes) and storage. |
40 | 49 | additionalContent: | |
| 50 | + ## Related content |
| 51 | +
|
| 52 | + - Frequently asked questions about Azure Cosmos DB for MongoDB](../faq.yml) |
| 53 | +
|
| 54 | + - [Get started with Azure Cosmos DB for MongoDB vCore using the Azure portal](quickstart-portal.md) |
| 55 | + - [Get started with Azure Cosmos DB for MongoDB vCore using Bicep](quickstart-bicep.md) |
41 | 56 |
|
42 | | - ## Next steps |
43 | | - |
44 | | - * [Build a .NET web app using Azure Cosmos DB's API for MongoDB](create-mongodb-dotnet.md) |
45 | | - * [Create a console app with Java and the API for MongoDB in Azure Cosmos DB](quickstart-java.md) |
| 57 | + ## Next step |
46 | 58 |
|
| 59 | + > [!div class="nextstepaction"] |
| 60 | + > [Frequently asked questions about Azure Cosmos DB](../../faq.yml) |
0 commit comments