Soru

Zorluk: KolayAssess and Select Migration Strategy (7 Rs)

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?

  1. A
    Rehost
  2. B
    Refactor
  3. ReplatformCevap
  4. D
    Relocate

Cevap

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.

Adım Adım Çözüm

1
Analyze the migration goals and constraints.
Goals: Eliminate operational burden of database patching, backups, and maintenance. Constraints: No modification of application source code, no database engine change.
Establishing clear requirements guides the selection of the correct migration strategy from the 7 Rs.
2
Evaluate the migration strategies against the constraints.
Rehosting on EC2 does not remove administrative overhead. Refactoring to Aurora requires database engine and application code changes. Replatforming to Amazon RDS for SQL Server maintains the engine, requires no application changes, and offloads operational overhead.
Comparing strategies ensures the selected path meets all requirements without violating constraints.
3
Select the optimal strategy.
Replatform is selected as it satisfies both the managed service goal and the zero-code-change constraint.
This strategy aligns perfectly with the 'tinker and shift' model of Replatforming.

Anahtar Kavram

Selecting the appropriate migration strategy (Replatforming vs. Rehosting vs. Refactoring) based on constraints like code change allowance and operational overhead reduction.
Bu soruyu puanla