Overview
Cloud application modernization is the work of moving existing applications onto cloud infrastructure and, where it pays off, changing how they are built and run so they scale, stay secure and cost less to operate. It is rarely one decision for the whole portfolio. Each application gets its own path, depending on its business value, its technical condition and how much change your team can absorb.
That is why we start with an assessment. We look at what each application does, what it depends on and what it costs to run today, then recommend a path for each one, including which applications to retire. Application modernization usually goes hand in hand with infrastructure modernization and data modernization, and we plan them together.
Modernization paths
What it usually improves
Modernization paths
Most portfolios use all three paths. Google Cloud provides purpose-built migration tooling for the first two, and we choose between them application by application.
Move virtual machines to Google Cloud without redesigning them. Migrate to Virtual Machines supports sources including vSphere on-premises data centers, AWS, Azure and Google Cloud VMware Engine, so it is a fast first step when the goal is to exit a data center or another cloud.
Learn more →Move traditional applications off VM instances and into native containers on Google Kubernetes Engine (GKE), including Autopilot clusters, or on Cloud Run. Migrate to Containers works with VMs on VMware or Compute Engine, including IBM WebSphere, JBoss, Apache, Tomcat, WordPress and Windows IIS applications.
Learn more →Rebuild the applications that deliver the most value as services on Cloud Run or GKE, so they scale with demand and release more often. We reserve this path for the applications where the business case is clear.
Talk to an architect →Platform choice
Both run containers, and both are good answers. The difference is how much of the platform you want to operate.
We decide per workload, and you can use both in the same environment: Cloud Run for services and jobs that should scale with demand, and GKE for applications built around Kubernetes.
API management
Apigee is part of the Google Cloud product family. Apigee simplifies API management and offers powerful analytics to optimize customer experiences and drive revenue growth, bolstering competitiveness in the digital era.
Apigee is used in
Apigee in industries
It is the process of moving applications to the cloud and, where it makes sense, changing how they are built and run so they scale better, cost less to operate and are easier to change. Options range from rehosting an application as-is to rebuilding it as cloud-native services.
No. Many applications can be moved as-is or containerized with tools such as Migrate to Virtual Machines and Migrate to Containers. We recommend rewriting only where the business case supports it.
Cloud Run suits containerized services and jobs that should scale with demand without cluster management. GKE, including Autopilot, suits applications built around Kubernetes. We choose per workload, and you can use both.
Apigee lets you manage, secure and monitor the APIs that connect legacy and modern systems, so you can modernize one application at a time without breaking the others. Read why Apigee.
It depends on the size of the portfolio and the path chosen for each application. We begin with an assessment and a pilot application so you have a realistic plan before you commit to the full program. Book a discovery call.
Often. Applications that expose clean APIs and run on managed platforms are easier to connect to Gemini and to Gemini Enterprise Agent Platform (formerly Vertex AI). See our guide to Vertex AI and our Gemini services.
