Diagram
A decision tree that starts with a workload and branches on its fit criteria to recommend rehost (lift and shift), refactor (move and improve), or rebuild (rip and replace), with Google Cloud examples for each path.
Choosing a Migration Path for Each Workload
Choosing a migration path means matching each workload or application tier to the approach that fits its dependencies, constraints, and business value. It is not necessary to use one approach for everything, and different tiers of the same stack can follow different paths. For example, a backend self-hosted MySQL database can be replatformed to Cloud SQL, frontend VMs can be refactored to containers on GKE Autopilot, where Google manages nodes, scaling, security, and other preconfigured settings, and hardware load balancing plus web application firewall (WAF) capabilities can be replaced with Cloud Load Balancing and Google Cloud Armor.
Domain 1 of 3
22 practice questions
Practice this DomainLast updated