A company runs MySQL database workloads on self-managed servers in an on-premises data center. The company wants to migrate the database workloads to an AWS managed service.
Which migration strategy should the company use?
A company runs MySQL database workloads on self-managed servers in an on-premises data center. The company wants to migrate the database workloads to an AWS managed service.
Which migration strategy should the company use?
Replatforming is the process of moving applications to the cloud with minimal changes but leveraging cloud-native features. When migrating a self-managed MySQL database to an AWS managed service like Amazon RDS for MySQL, which offers fully managed operations, this strategy fits best. The aim is to benefit from AWS's managed database services' operational efficiency and cost-effectiveness while requiring fewer changes compared to refactoring.
Replatform because we are going to from self managed db to fully managed db by aws so it's not sufficient rehost.
D is correct. please help with discussion on 500 503 ~ 511. Thanks.
The answer is D, Replatform. https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-guide/migration-strategies.html This strategy is also known as lift, tinker, and shift or lift and reshape. Using this migration strategy, you move the application to the cloud, and you introduce some level of optimization in order to operate the application efficiently, to reduce costs, or to take advantage of cloud capabilities. For example, you might replatform a Microsoft SQL Server database to Amazon RDS for SQL Server. Using this strategy, you might make a few or many changes to the application, depending on your business goals and your target platform. The following are common use cases for the replatform migration strategy: You want to save time and reduce cost by moving to a fully managed service or serverless service in the AWS Cloud.
Why not A, rehost? Is it because Rehost is more used for applications and Replatform is used for databases?