This post is a part of the DP-900: Microsoft Azure Data Fundamentals Exam Prep Hub.
This topic falls under these sections:
Describe considerations for working with non-relational data on Azure (15–20%)
--> Describe capabilities and features of Azure Cosmos DB
--> Identify use cases for Azure Cosmos DB
Note that there are 10 practice questions (with answers and explanations) for each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available on the hub below the exam topics section.
Azure Cosmos DB is a fully managed, globally distributed database service designed for modern applications that require low latency, massive scalability, and flexible data models.
For the DP-900 exam, you should understand when and why to use Azure Cosmos DB, especially compared to other Azure storage and database services.
What Is Azure Cosmos DB?
Azure Cosmos DB is a NoSQL, multi-model database service that supports:
- Global distribution across multiple regions
- Low-latency reads and writes
- Automatic scaling
- Multiple APIs (Core SQL, MongoDB, Cassandra, Table, Gremlin)
✔ It is designed for high-performance, internet-scale applications.
Key Characteristics That Drive Use Cases
Understanding Cosmos DB use cases starts with its capabilities:
1. Global Distribution
- Replicate data across multiple Azure regions
- Users access data from the closest region
✔ Enables global applications with low latency
2. Low Latency
- Single-digit millisecond response times
- Ideal for real-time applications
3. Massive Scalability
- Scales throughput and storage independently
- Handles millions of requests per second
4. Flexible Schema
- Schema-less (JSON-based data model)
- Supports evolving application requirements
5. Multiple APIs
- Supports different data models:
- SQL (Core API)
- MongoDB
- Cassandra
- Table
- Gremlin (graph)
✔ Allows developers to use familiar tools and frameworks
Common Use Cases for Azure Cosmos DB
1. Global Web and Mobile Applications
Scenario
Applications with users distributed worldwide.
Why Cosmos DB?
- Global distribution
- Low latency access
- High availability
✔ Example:
- Social media platforms
- E-commerce applications
2. Real-Time Personalization
Scenario
Applications that tailor content to users instantly.
Why Cosmos DB?
- Fast read/write performance
- Flexible schema
✔ Example:
- Product recommendations
- Personalized dashboards
3. IoT and Telemetry Data
Scenario
Large volumes of streaming data from devices.
Why Cosmos DB?
- High ingestion rates
- Scalable storage
- Schema flexibility
✔ Example:
- Sensor data collection
- Smart devices
4. Gaming Applications
Scenario
Online games requiring real-time interactions.
Why Cosmos DB?
- Low latency
- Global availability
- High throughput
✔ Example:
- Leaderboards
- Player profiles
- Game state storage
5. E-commerce Platforms
Scenario
High-traffic applications with variable workloads.
Why Cosmos DB?
- Elastic scalability
- Fast performance
- Global distribution
✔ Example:
- Shopping carts
- Product catalogs
6. Content Management Systems
Scenario
Managing diverse and evolving content.
Why Cosmos DB?
- Schema-less design
- Flexible data models
✔ Example:
- Blogs
- Media platforms
7. Event-Driven and Microservices Architectures
Scenario
Modern distributed applications.
Why Cosmos DB?
- Scales independently per service
- Supports high-throughput operations
✔ Example:
- Microservices storing independent datasets
When NOT to Use Azure Cosmos DB
Cosmos DB is not ideal when:
- You need complex joins and relational queries
- You require strict relational consistency across multiple tables
- Your workload is small and cost-sensitive
✔ In these cases, relational databases like Azure SQL may be more appropriate.
Cosmos DB vs Other Azure Storage Options
| Service | Best For |
|---|---|
| Blob Storage | Unstructured files (images, videos) |
| Azure Files | File shares |
| Table Storage | Simple key-value storage |
| Cosmos DB | Global, high-performance NoSQL apps |
Why This Matters for DP-900
On the exam, you may be asked to:
- Identify appropriate Cosmos DB use cases
- Choose Cosmos DB for global, low-latency applications
- Compare it with other Azure storage services
- Recognize scenarios requiring scalability and flexibility
Summary — Exam-Relevant Takeaways
✔ Azure Cosmos DB = globally distributed NoSQL database
✔ Key strengths:
- Low latency
- Global distribution
- Massive scalability
- Flexible schema
✔ Common use cases:
- Global apps
- Real-time personalization
- IoT and telemetry
- Gaming
- E-commerce
✔ Not suitable for:
- Complex relational workloads
- Heavy join operations
✔ Key decision factor:
👉 High scale + low latency + global users = Cosmos DB
Go to the Practice Exam Questions for this topic.
Go to the DP-900 Exam Prep Hub main page.
