Google Cloud Next is now in its second day. Google Cloud emphasizes the new innovative capabilities of its platform, but given that many enterprise workloads are still traditional legacy workloads, such as those written in Java, or off-the-shelf ones purchased and deployed many years ago, Google Cloud either possesses, or recently announced, elements that assist customers in the journey.
There are virtual machine migration tools as well as App Engine Flexible that supports language runtimes. Better VPCs and VPNs enable creation of hybrid clouds or shared projects with a common network. These are just a few of their offerings that fill in “holes” in their offerings before. These are areas that people often overlook when looking at Google Cloud.
What’s important is for enterprises to 1) assess where they are, 2) determine where they want to get to as the end-state, 3) perform a gap analysis, and 4) determine the journey. It’s so easy to categorically say that all customers need to do XYZ to migrate from legacy infrastructure to the cloud. There is a spectrum of users with their use cases. So each path is different. Some enterprises are mature in knowing who they are, where they are today, and where they want to go.
The value of professional services, or processes such as Value Engineering (popularized by firms like SAP) are important to help customers make the transformation.