Microsoft Azure Data FundamentalsDescribe how to work with non-relational data on AzureMedium
A data engineer is designing a data ingestion pipeline for real-time telemetry data from thousands of IoT devices. Each telemetry event is a small JSON document. The solution requires high throughput, low latency reads and writes, and flexible schema support for evolving data models. Which Azure Cosmos DB API is the most appropriate choice?
- AAzure Cosmos DB for Table API
- BAzure Cosmos DB for Cassandra API
- CAzure Cosmos DB for Gremlin (Graph) API
- DAzure Cosmos DB for NoSQL (Core) API
Show answer & explanationAnswer & explanation
Correct answer: D. Azure Cosmos DB for NoSQL (Core) API
The Azure Cosmos DB for NoSQL (Core) API is designed for document-oriented data, offering high throughput, low latency, and flexible schema capabilities, making it ideal for ingesting and querying JSON telemetry data.
Why the other options are wrong
- A. Table API is for simple key-value pairs, not ideal for rich JSON documents.
- B. Cassandra API is for column-family data, often used for migrating existing Cassandra workloads.
- C. Gremlin API is for graph data, not primarily for telemetry event ingestion.
Azure Cosmos DB for NoSQL (Core) API
The native API for Azure Cosmos DB, designed for document data (JSON), offering high performance, flexible schema, and global distribution.
- Supports JSON documents natively.
- Offers five consistency models.
- Ideal for web, mobile, and IoT applications requiring low-latency access.
Memory trick: NoSQL for JSON speed, Gremlin for connections, Table for simple, Cassandra for wide columns.