Which strategy should the solutions architect choose to perform this migration?
Create a fleet of EC2 instances. Install MongoDB Community Edition on the EC2 instances, and create a database. Configure continuous synchronous replication with the database that is running in the on-premises data center.
Create an AWS Database Migration Service (AWS DMS) replication instance. Create a source endpoint for the on-premises MongoDB database by using change data capture (CDC). Create a target endpoint for the Amazon DocumentDB database. Create and run a DMS migration task.
Create a data migration pipeline by using AWS Data Pipeline. Define data nodes for the on-premises MongoDB database and the Amazon DocumentDB database. Create a scheduled task to run the data pipeline.
Create a source endpoint for the on-premises MongoDB database by using AWS Glue crawlers. Configure continuous asynchronous replication between the MongoDB database and the Amazon DocumentDB database.
Explanations:
This option involves setting up EC2 instances with MongoDB Community Edition, which would not facilitate a smooth migration to Amazon DocumentDB. Instead of creating a new MongoDB instance, a more direct and efficient method is required to migrate the data to DocumentDB. Additionally, continuous synchronous replication is not supported in this scenario, as DocumentDB is not designed to be a direct MongoDB replica.
Using AWS Database Migration Service (DMS) is a suitable approach for migrating data from an on-premises MongoDB database to Amazon DocumentDB. By creating a replication instance and configuring change data capture (CDC) for ongoing replication, this method efficiently migrates data and keeps it in sync during the transition. This is the most recommended approach for such a migration.
AWS Data Pipeline is not ideal for real-time migration scenarios. It is primarily used for batch processing of data and lacks the capabilities of ongoing replication, which is essential for migrating a live database without downtime. This method would not facilitate a smooth transition to Amazon DocumentDB and is not aligned with the requirement for an efficient migration.
AWS Glue is designed for data transformation and ETL processes, rather than real-time replication or migration of databases. While it can help in moving data, it does not support continuous replication required for the live migration of a MongoDB database to Amazon DocumentDB. This method would also result in higher latency and potential data inconsistencies during migration.
I suspect that the answer is:
Create an AWS Database Migration Service (AWS DMS) replication instance. Create a source endpoint for the on-premises MongoDB database by using change data capture (CDC). Create a target endpoint for the Amazon DocumentDB database. Create and run a DMS migration task.
In my opinion, the answer is:
Create an AWS Database Migration Service (AWS DMS) replication instance. Create a source endpoint for the on-premises MongoDB database by using change data capture (CDC). Create a target endpoint for the Amazon DocumentDB database. Create and run a DMS migration task.