An organization is architecting a globally distributed storage solution using Azure Cosmos DB. The system must support four distinct application components, each with unique data access patterns, migration origins, and scaling requirements. The components must be highly resilient across multiple Azure regions, support sub-10ms read/write latencies, and minimize code changes during migration from legacy environments.
Match each application requirement on the left to the correct Azure Cosmos DB API on the right to align with the workloads.
- A migration of an on-premises time-series telemetry store that utilizes Column Family data structures, requiring native Cassandra Query Language (CQL) queries.API for Cassandra
- A new social media analysis tool mapping complex user relationships, shared interests, and multi-layered hierarchies using graph traversal algorithms.API for Gremlin
- A global catalog application requiring transactional execution, JSON document indexing, and ad-hoc SQL-like SELECT queries.API for NoSQL
- An e-commerce shopping cart service migrated from an open-source document store, requiring BSON document compatibility and driver reuse.API for MongoDB
Cevap
Match Cassandra Query Language queries to the API for Cassandra; match graph relationships to the API for Gremlin; match SQL-like JSON document queries to the API for NoSQL; and match BSON document workloads to the API for MongoDB.
Each application component is matched to its corresponding Cosmos DB API based on its storage model (wide-column, graph, document) and the compatibility needs of legacy queries.
Adım Adım Çözüm
Anahtar Kavram
Azure Cosmos DB Multi-Model APIs