Diagram
A decision tree that routes a legacy workload based on its dependencies and value: rehost when it moves as-is, refactor when dependencies must be untangled, and rebuild when it no longer satisfies requirements.
Choosing Rehost Versus Refactor and Rebuild
Choosing between migration paths depends on the workload's dependencies, condition, and business value:
| Migration path | What changes | Choose when |
|---|---|---|
| Rehost (lift and shift) | Workload moves as-is or with minimal code or configuration changes | Workload has few dependencies, is not worth refactoring or cannot be refactored before migration, or is based on third-party software |
| Refactor (move and improve) | Workload is modified to take advantage of cloud capabilities | Dependencies must be untangled, workload relies on systems that cannot be accommodated in the cloud, or it does not use compute or storage efficiently |
| Rebuild (remove and replace) | Application is decommissioned and rewritten as cloud-optimized | Workload no longer satisfies requirements, can be replaced, uses end-of-life technology, or has uneconomical license fees |
Domain 6 of 6
27 practice questions
Practice this DomainLast updated