Skip to content

Commit 0297acd

Browse files
committed
updates
1 parent f30f585 commit 0297acd

File tree

3 files changed

+6
-23
lines changed

3 files changed

+6
-23
lines changed

01_Overview_Cosmos_DB/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Overview of Azure Cosmos DB (high-level with links to docs for more information)
1+
# Overview of Azure Cosmos DB
22

33
[Azure Cosmos DB](https://learn.microsoft.com/en-us/azure/cosmos-db/introduction) is a globally distributed, multi-model database service that enables you to query and store data using NoSQL models using one of five APIs: SQL (document database), Cassandra (column-family), MongoDB (document database), Azure Table, and Gremlin (graph database). It provides turnkey global distribution, elastic scaling of throughput and storage worldwide, single-digit millisecond latencies at the 99th percentile, and guaranteed high availability with multi-homing capabilities. Azure Cosmos DB provides comprehensive service level agreements (SLAs) for throughput, latency, availability, and consistency guarantees, something not found in any other database service.
44

@@ -12,7 +12,7 @@ The [RU architecture](https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/
1212

1313
Azure Cosmos DB for MongoDB [vCore architecture](https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/vcore/introduction) integrates AI-based applications with your data, with text indexing for easy querying. Simplify your development process with high-capacity vertical scaling and free 35-day backups with a point-in-time restore (PITR).
1414

15-
The [choice between vCore and Request Units (RU)](https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/choose-model) in Azure Cosmos DB for MongoDB API depends on the workload.
15+
The [choice between vCore and Request Units (RU)](https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/choose-model) in Azure Cosmos DB for MongoDB API depends on the workload. A list of [compatibility and feature support between RU and vCore](https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/vcore/compatibility) is available.
1616

1717
vCore provides predictable performance and cost and is ideal for running high-performance, mission-critical workloads with low latency and high throughput. With vCore, the number of vCPUs and the memory the database needs is configurable and can be scaled up or down as needed.
1818

06_Create_First_Cosmos_DB_Project/README.md

Lines changed: 2 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ For Windows machines, the emulator can be installed via an installer. There is a
1212

1313
Learn more about the pre-requisites and installation of the emulator [here](https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-develop-emulator?tabs=windows%2Cpython&pivots=api-mongodb).
1414

15-
>**NOTE**: When using the Azure CosmosDB emulator using the API for MongoDB it must be started with the [MongoDB endpoint options enabled](https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-develop-emulator?tabs=windows%2Cpython&pivots=api-mongodb#start-the-emulator) on the command-line.
15+
>**NOTE**: When using the Azure CosmosDB emulator using the API for MongoDB it must be started with the [MongoDB endpoint options enabled](https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-develop-emulator?tabs=windows%2Cpython&pivots=api-mongodb#start-the-emulator) at the command-line.
1616
1717
**The Azure Cosmos DB emulator does not support vector search. To complete the vector search and AI-related labs, you must use an Azure Cosmos DB API for the MongoDB vCore account in Azure.**
1818

@@ -28,27 +28,10 @@ The splash screen or **Quickstart** section of the Cosmos DB Emulator will displ
2828

2929
### Retrieving the connection string from the Azure portal
3030

31-
Retrieve the connection string from the Azure portal by navigating to your Azure Cosmos DB account and selecting the **Connection String** menu item on the left-hand side of the screen. The connection string contains tokens for the username and password that must be replaced with the username and password used when provisioning the Azure Cosmos DB API for MongoDB service. Users can be added at any time using the [Azure CLI](https://learn.microsoft.com/en-us/cli/azure/cosmosdb/mongodb/user?view=azure-cli-latest).
31+
Retrieve the connection string from the Azure portal by navigating to your Azure Cosmos DB account and selecting the **Connection String** menu item on the left-hand side of the screen. The connection string contains tokens for the username and password that must be replaced with the username and password used when provisioning the Azure Cosmos DB API for MongoDB service.
3232

3333
![The Azure CosmosDb API for MongoDB Connection strings screen displays with the copy button next to the connection string highlighted.](media/azure_connection_string.png)
3434

35-
## Authorization
36-
37-
Azure Cosmos DB API for MongoDB supports fine-grained role-based access control (RBAC) for authorization. There are several built-in roles available. The built-in roles are:
38-
1. read
39-
2. readWrite
40-
3. dbAdmin
41-
4. dbOwner
42-
43-
The ability to create custom roles is also available. Custom roles can be created using the [Azure CLI](https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/how-to-setup-rbac). Customized roles can include granular permissions for specific databases, collections, and operational actions. Learn more about the [Azure CLI RBAC commands to define custom roles](https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/how-to-setup-rbac#azure-cli-rbac-commands).
44-
45-
## Helpful tools
46-
47-
Visualization and querying tools:
48-
1. Studio 3T
49-
2. MongoDB Compass
50-
3. MongoDB Shell
51-
5235
## Lab 1 - Create your first Cosmos DB for the MongoDB application
5336

5437
Using a notebook, we'll create a Cosmos DB for the MongoDB application in this lab. You can use the Azure Cosmos DB Emulator or an Azure Cosmos DB account in Azure. The following concepts will be covered in this lab:

07_Load_Data/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,8 @@ When loading data, bulk operations are preferred over adding each document indiv
1212

1313
4. Simplified code logic: By using bulk operations, the lab can simplify its code logic and reduce the number of database queries. This results in cleaner, more manageable code and reduces the likelihood of errors or inconsistencies.
1414

15-
## Lab 3 - Load data into Azure Cosmos DB API for MongoDB collections
15+
## Lab 2 - Load data into Azure Cosmos DB API for MongoDB collections
1616

1717
This lab will load the Cosmic Works Customer, Product, and Sales data into Azure Cosmos DB API for MongoDB collections using bulk operations.
1818

19-
Please complete Lab 3 in the lab repository.
19+
Please complete Lab 2 in the lab repository.

0 commit comments

Comments
 (0)