Migration paths

Six answers for a workload, ordered by how much changes

Discovery and assessment: list every workload, what it depends on, and what it is worthRetireswitch it offan unusedreporting toolRetainleave it for nowa system dueto be replacedRehostmove it as it isservers becomeCompute Engine VMsReplatformsmall changesthe database goesto Cloud SQLRefactorredesign for cloudrebuilt as serviceson GKE or Cloud RunReimaginerethink the processpaper claims becomean AI-led servicehow much the application changesEvery workload gets one of six answers, and they differ in how much is changed.A workload is one application with everything it needs to run. Rehosting is quickest and gains least.Refactoring and reimagining cost most and gain most. Most plans use all six, application by application.

Retire, retain, rehost, replatform, refactor or reimagine, after assessing every workload.

Migration paths · Going deeper

The eight migration terms

Migration termsWorkloadAn application, with the data and resources it needs to runDiscovery and assessmentFinding every workload and judging how, and whether, to move itRetireDecommission it: nobody needs it any moreRetainKeep it where it is, for now or for goodRehost"Lift and shift": the same application on cloud virtual machinesReplatform"Lift and optimise": small changes to use a managed serviceRefactorChange the design or code to use cloud features fullyReimagineRethink the business process itself, with cloud and AIRehost changes where it runs. Replatform changes what it runs on. Refactor changes how it is built.Reimagine changes what the business does, which is why it sits closest to digital transformation.

Rehost moves it, replatform adjusts it, refactor rebuilds it, reimagine rethinks it.

Running code

Three ways to run code, by how much Google runs for you

your codehow it scalesoperating systemserversCompute Enginevirtual machinesyouyouyouGoogleGKEcontainers on KubernetesyouyouGoogleGoogleCloud RunserverlessyouGoogleGoogleGoogleFrom left to right Google runs more, and you are left with only your code.Compute Engine gives a whole machine and full control. GKE runs containers and looks after Kubernetesfor you. Cloud Run takes a container and runs it on request, scaling to nothing when idle. More controlon the left, less work on the right.

Compute Engine gives machines, GKE runs containers, and Cloud Run leaves you only your code.

Running code · Going deeper · 1 of 2

Nine compute terms

Compute termsVirtual machineA computer made of software, with its own operating systemContainerAn application packaged with what it needs, sharing the host's operating systemKubernetesOpen source software that runs and heals many containersMicroservicesAn application built as small services that deploy and scale separatelyServerlessYou supply code; the provider runs and scales it; you pay only while it runsManaged serviceA service the provider operates, patches and backs up for youAutoscalingAdding and removing capacity automatically as demand changesLoad balancingSpreading requests across many copies, and around failed onesSpot VMsSpare capacity at a large discount, which can be taken back at any time

From virtual machine and container to autoscaling and Spot VMs.

Running code · Going deeper · 2 of 2

Which one to choose

Four places to run an applicationProductWhat it runsChoose it whenCompute EngineVirtual machinesyou need the operating system, or are rehostingGKEContainers, on managed Kubernetesmany services, and you want Kubernetes' controlCloud RunA container, serverlessa web service or API with no cluster to manageCloud Run functionsOne function, serverlessa small piece of code that reacts to an eventCloud Run runs a whole service. Cloud Run functions runs a single function when something happens.An uploaded file, a message or a web request can each trigger a function. Both scale to zero, so an idleservice costs nothing.

Cloud Run runs a service. Cloud Run functions runs one function on an event.

Check yourself

Packaged asa containerTo manageno servers and no clusterWhen idlepay nothing; scale up with requests

A team lists what it wants as shown. Which product fits?

Modern applications

Small services scale and fail one at a time

One applicationcataloguesearchcheckoutaccountscataloguesearchcheckoutaccountscataloguesearchcheckoutaccountsCheckout is busy, so everything is copied 3 times: 12 parts running.Four servicescataloguesearchaccountscheckoutcheckoutcheckoutOnly checkout is copied: 6 parts running.Small services scale, fail and change one at a time. One large application does all three as a whole.That is the case for modern application development: pay only for the part that is busy, lose only thepart that broke, and release one service without retesting the rest. Containers and managed servicesare what make so many small parts practical to run.

Copying a whole application runs 12 parts. As microservices, copying only the busy one runs 6.

Modern applications · Going deeper

The business value of modern apps

What modern application development is worthMicroservicesTeams release small parts separately, so change is faster and saferManaged servicesGoogle runs the databases, queues and clusters; staff build featuresCost optimisationEach part scales alone, and serverless parts cost nothing when idleResilienceOne failed service does not take the others downEfficiencyAutomation builds, tests and releases, with less manual workThe five are what the guide lists as the business value of modern application development.GKE adds automatic repair, upgrades and scaling of clusters, which is its own business case: Kuberneteswithout a team to operate Kubernetes.

Microservices, managed services, lower cost, resilience and efficiency.

Hybrid and multicloud

Five products work where your data already is

Your datacentreAnother cloudGoogle CloudAlloyDB Omnithe AlloyDB database, run where you chooseBigQuery Omnianalyse data in another cloud, without moving itGKE Enterprisemanage Kubernetes clusters everywhere, from one placeLookerone set of dashboards over data in any of themCloud SQLstandard open enginesFive products reach beyond Google Cloud, so you can modernise without moving everything first.Each bar covers the places the product works. The exam's point is openness: data and applications in yourown datacentre or another cloud can be run, analysed and managed with the same tools.

AlloyDB Omni, BigQuery Omni, GKE Enterprise, Looker and Cloud SQL reach beyond Google Cloud.

Hybrid and multicloud · Going deeper

The hybrid and multicloud products

Products that support hybrid and multicloudAlloyDB OmniA downloadable edition of AlloyDB that runs in your datacentre or in other cloudsBigQuery OmniBigQuery analysis of data held in other clouds, leaving the data where it isGKE EnterpriseOne way to manage and secure Kubernetes clusters wherever they runLookerBusiness intelligence that connects to many databases and cloudsCloud SQLStandard MySQL, PostgreSQL and SQL Server, so applications move without rewriting"Omni" means the Google product comes to the data. "Enterprise" on GKE means many clusters, many places.A question with data in another cloud that "cannot be moved" is pointing at an Omni product.

Omni means the Google product comes to the data.

Check yourself

BEFOREpayroll application on aserver in the officeAFTERthe same application, on aCompute Engine VM

Which migration path does the drawing show?

APIs

An API lets others build on what a company already does

What the airline hasseats, prices,bookingsAPIa defined wayto ask for itApigeechecks who is asking,limits and counts use,charges for itits own mobile apptravel sites and partnersAI agentsAn API turns something a company does into something others can build on, and pay for.An API is a contract between pieces of software: ask in this form, receive that. It lets old systems servenew applications without being rewritten. Offered to outsiders, it becomes a product with its own revenue.Apigee is the manager at the door: security, limits, analytics and billing for every API.

An API is a defined way to ask for a capability. Apigee secures, measures and monetises it.

APIs · Going deeper · 1 of 2

What Apigee does

What Apigee API Management doesSecurityChecks keys and identities, and blocks abuse, before a request reaches your systemsTraffic controlSets limits so one caller cannot overwhelm the serviceAnalyticsShows who calls which API, how often, and how fast it answersDeveloper portalWhere partners find the APIs, read how to use them and sign upMonetisationPlans and billing: charge by call, by tier or by revenue shareAny backendFronts systems in Google Cloud, in other clouds and on-premisesAPIs create new business by letting partners, and now agents, do business with you automatically.Monetising a public API is the guide's phrase. Apigee is the product named for managing it.

Security, traffic control, analytics, a developer portal and monetisation.

APIs · Going deeper · 2 of 2

Clue words for modernisation

When the question saysThe answer isBecause it is"lift and shift", "as is", "fastest"Rehostsame application, new place"minor changes", "managed database"Replatformlift and optimise"re-architect", "microservices"Refactorredesigned for cloud"no longer needed"Retireswitch it off"full control of the OS", "licences"Compute Enginevirtual machines"orchestrate containers"GKEmanaged Kubernetes"container, no infrastructure to manage"Cloud Runserverless containers"run code when a file arrives"Cloud Run functionsevent-driven function"fault-tolerant batch job, lowest price"Spot VMsspare capacity"clusters on-premises and in other clouds"GKE Enterpriseone way to manage all"analyse data that stays in another cloud"BigQuery OmniBigQuery comes to the data"expose, secure and monetise APIs"ApigeeAPI managementSection 4 has three lists: migration paths, places to run code, and products that reach other clouds.

Three lists: migration paths, places to run code, and hybrid products.

Check yourself

the bank'spayment system?lets approved partners in,counts every call,bills them for usefintechpartners

A bank wants what the drawing shows. Which product belongs at the "?"

Lesson complete

You finished “Modernising infrastructure and applications”

Answer the questions along the way to see your score here.

Open in a new tab