Examkin

Question

Difficulty: EasyAzure Cosmos DB and NoSQL Solutions

You are designing a data storage solution using Azure Cosmos DB for a multi-region retail application. The application requires global distribution across three Azure regions, a 99.999% availability SLA for both reads and writes, and a 90/10 read-to-write ratio. Match each application workload to the most appropriate Azure Cosmos DB API.

  • API for NoSQLA customer order catalog that requires JSON document storage and querying using SQL syntax.
  • API for MongoDBA shopping cart session service migrating from an on-premises MongoDB database without changing the application logic.
  • API for GremlinA recommendation engine that maps and traverses complex relationships between customers, products, and reviews.

Answer

API for NoSQL matches the customer order catalog; API for MongoDB matches the shopping cart session service migrating from MongoDB; API for Gremlin matches the recommendation engine traversing relationships.
The API for NoSQL is the native document model using SQL query syntax. The API for MongoDB supports wire-protocol compatibility for existing MongoDB codebases. The API for Gremlin supports graph databases using vertices and edges.

Step-by-Step Solution

1
Identify the data model and query language requirements for the customer order catalog workload.
The catalog requires JSON document storage and SQL querying, which directly aligns with the native Azure Cosmos DB API for NoSQL.
Matching workloads to their native APIs minimizes translation layers and provides the best performance and tooling support.
2
Identify the compatibility requirements for the shopping cart session service.
The workload is migrating from MongoDB and requires compatibility without application code changes, which maps to the API for MongoDB.
The API for MongoDB implements the wire protocol of MongoDB, allowing existing drivers and tools to work out-of-the-box.
3
Identify the relationship and traversal requirements for the recommendation engine.
The engine requires traversing relationships between entities, representing a graph data structure, which maps to the API for Gremlin.
The API for Gremlin supports property graphs and the Gremlin query language, which is standard for graph database traversals.

Key Concept

Azure Cosmos DB API selection based on workload data models and compatibility requirements.
Rate this question

Topics

Azure Cosmos DB and NoSQL Solutions

More questions from this topic