A company is planning to migrate its on-premises customer relationship management (CRM) application to AWS. The application's backend database runs on Microsoft SQL Server. The primary goal of the migration is to eliminate the operational burden of database patching, backups, and OS-level maintenance. However, the company has strict timeline constraints and cannot modify the application's source code or change the database engine.
Which migration strategy should the company select for the database?
- ARehost
- BRefactor
- ReplatformAnswer
- DRelocate
Answer
Replatform
Replatforming (often called 'tinker and shift') is the best choice because migrating the Microsoft SQL Server database to Amazon RDS for SQL Server allows the database engine to remain the same and requires no application code changes, while successfully offloading the operational tasks of patching, backups, and OS-level administration to AWS.
Step-by-Step Solution
Key Concept
Selecting the appropriate migration strategy (Replatforming vs. Rehosting vs. Refactoring) based on constraints like code change allowance and operational overhead reduction.