You are designing the storage architecture for an enterprise modernization project. You need to match the application workloads and migration requirements to the most appropriate Azure Cosmos DB API. To answer, match each workload scenario on the left with its corresponding Azure Cosmos DB API on the right.
- A modernized e-commerce shopping cart service requiring JSON document storage, SQL-like querying over hierarchical data, and enterprise-grade multi-region writes.API for NoSQL
- A real-time fraud detection engine that models and queries highly connected multi-hop relationships and dependency networks among entities.API for Gremlin
- A migration of a legacy wide-column telemetry database that executes Cassandra Query Language (CQL) queries, requiring minimal codebase changes.API for Cassandra
- A customer profile database migration from an on-premises database that uses native BSON serialization and requires compatibility with existing MongoDB driver libraries.API for MongoDB
Answer
Match the e-commerce shopping cart to API for NoSQL, the fraud detection engine to API for Gremlin, the wide-column telemetry database to API for Cassandra, and the customer profile database to API for MongoDB.
The correct matches align the workload patterns and migration specifications to their respective Azure Cosmos DB API wire protocols: native SQL queries on JSON documents map to API for NoSQL; graph and relationship traversals map to API for Gremlin; wide-column CQL workloads map to API for Cassandra; and BSON-based document workloads map to API for MongoDB.
Step-by-Step Solution
Key Concept
Azure Cosmos DB API selection based on workload characteristics and migration requirements.
Estimated Time:2m 0s