Question

A retail company runs a self-managed Apache Cassandra cluster on 12 EC2 instances backing its product catalog service. Operations staff spend significant time patching nodes, managing repairs, and scaling the ring during seasonal peaks. Leadership wants to eliminate this operational burden while keeping the existing CQL-based application code changes to an absolute minimum, and they require the migration cutover to complete with less than 5 minutes of write downtime. Which approach best meets these requirements?

Accepted Answer

Migrate to Amazon Keyspaces (for Apache Cassandra) using the CQL COPY command for historical data plus a temporary dual-write from the application to both clusters during cutover, then switch reads to Keyspaces.

Answer

Migrate the data to Amazon DynamoDB using AWS Glue to transform the schema, and rewrite the application to use the DynamoDB SDK.

Answer

Rehost the Cassandra cluster onto larger EC2 instances in an Auto Scaling group and use AWS Backup to reduce the operational effort of the ring.

Answer

Use AWS Database Migration Service (DMS) with a full-load-plus-CDC task to replicate the Cassandra cluster into Amazon Aurora PostgreSQL.