From the course: Microsoft Azure Cosmos DB Developer Specialty (DP-420) Cert Prep: 1 Design and Implement Data Models by Microsoft Press

Unlock this course with a free trial

Join today to access over 23,200 courses taught by industry experts.

Develop a design by storing multiple related entities in the same document

Develop a design by storing multiple related entities in the same document - Azure Tutorial

From the course: Microsoft Azure Cosmos DB Developer Specialty (DP-420) Cert Prep: 1 Design and Implement Data Models by Microsoft Press

Start my 1-month free trial Buy for my team

Develop a design by storing multiple related entities in the same document

“

What we're dealing with in this section of the objectives are some data model and architectural concerns. First of all, how do we measure Cosmos DB performance? If you've used other Azure platform as a service products, you probably know about Azure Monitor and Log Analytics, and you know about all that kind of stuff. Well, in Cosmos it's pretty much the same idea. In other words, we're concerned with latency. In other words, requests that come from your client application into your Cosmos DB account endpoint, ultimately the containers, we're dealing with, what is the wait time involved? Now, this is going to lead you to think of a number of things, but one would be, "Do you want to replicate your Cosmos account to multiple regions to put those instances of your data containers closer to the users who are consuming your application?" And you can do those replicas either read-only or read-write all across the Azure Commercial Cloud. The other performance metric with Cosmos besides…

Contents