Microsoft Azure Data FundamentalsDescribe how to work with non-relational data on AzureEasy
A company is migrating its on-premises application that uses Apache Cassandra to Azure. The application requires high availability, global distribution, and needs to minimize code changes during migration. Which Azure non-relational data service should they choose to host their Cassandra database?
- AAzure Virtual Machines with Cassandra installed
- BAzure Cosmos DB with Cassandra API
- CAzure Table Storage
- DAzure Database for PostgreSQL (with Cassandra extension)
Show answer & explanationAnswer & explanation
Correct answer: B. Azure Cosmos DB with Cassandra API
Azure Cosmos DB with the Cassandra API provides a fully managed, globally distributed Cassandra-compatible database service. This allows the company to migrate their existing Cassandra applications with minimal code changes while leveraging Cosmos DB's native high availability, global distribution, and automatic scaling capabilities.
Why the other options are wrong
- A. Running Cassandra on Azure Virtual Machines requires significant management overhead for high availability, global distribution, and scaling, which the company wants to avoid.
- C. Azure Table Storage is a simple key-value store and is not compatible with Apache Cassandra.
- D. Azure Database for PostgreSQL is a relational database and does not natively support Cassandra, nor is there a direct 'Cassandra extension' for it.
Azure Cosmos DB Cassandra API
A fully managed, globally distributed database service compatible with Apache Cassandra.
- Compatible with existing Apache Cassandra SDKs and tools.
- Leverages Cosmos DB's global distribution and high availability.
- Eliminates the need for Cassandra cluster management.
- Ideal for migrating existing Cassandra workloads to Azure.
Memory trick: Cassandra API for easy migration, VMs for hard work.