Question

A company runs a self-managed MongoDB 4.0 cluster on EC2 instances that backs a customer-facing application. Leadership wants to reduce operational overhead by moving to a managed service while keeping the application code and its existing driver-based queries essentially unchanged. The migration must minimize downtime, and the current dataset is 800 GB with active writes throughout the day. Which approach best meets these requirements?

Accepted Answer

Use AWS DMS with a full load plus change data capture (CDC) task to migrate the collections into Amazon DocumentDB, then create indexes on the target and cut over after replication lag is near zero.

Answer

Refactor the data model into Amazon DynamoDB tables, use the AWS Schema Conversion Tool to convert queries, and dual-write from the application during a phased cutover.

Answer

Take a mongodump snapshot, copy it to Amazon S3 with DataSync, and mongorestore it into a new self-managed MongoDB cluster on larger EC2 instances during a maintenance window.

Answer

Migrate the database to Amazon RDS for PostgreSQL using DMS heterogeneous replication and rewrite the application to use SQL queries against the relational schema.