Blog Post

New networking features make hybrid clouds possible on Google Compute Engine

Stay on Top of Emerging Technology Trends

Get updates impacting your industry from our GigaOm Research Community
Join the Community!

Toward the tail end of Google I/O on Friday, Sunil James, a Google product manager (on left in picture), and John Cormie, a software engineer focusing on networking for Google Compute Engine (GCE), showed off new network capabilities for GCE that can enable hybrid clouds running between GCE deployments and on-premise data centers.

GCE customers are now able to do things like establish virtual private Layer 3 networks and assign static public IP addresses to instances, James said. Connecting networks will also become possible. And a load-balancing service is on the way “as part of the native fabric for Google Compute Engine,” James said.

Developers interested in trying out GCE load balancing can fill out a form to do so. Developers can also sign up for early access to all emerging Google Cloud Platform features.

The load balancing and routing services are the sorts of things that could help more businesses make the decision to try real projects on the newly publicly available Infrastructure as a Service (IaaS) piece of the Google Cloud Platform.

And the new capabilities move Google a few steps closer campaign to becoming a top, widely used IaaS provider — if not one day bigger than Amazon Web Services (s amzn) then at least No. 2. That position is already feasible for Google as it is.

2 Responses to “New networking features make hybrid clouds possible on Google Compute Engine”

  1. Robert Jenkins

    At this stage it isn’t clear how this hybrid connection will work for GCE. What customers really want is a transparent ability to plug private networks in the public cloud into their own private in-house infrastructure over a physical patch. That means a transparent patch that can carry both layer 2 and layer 3 traffic at full line speed without the overhead of a VPN etc. and without needing public IP addresses.

    This is critical because most customers using these hybrid set-ups want an all private IP solution, they don’t want public IP exposure and they want to see their networks in both the public and private end in the same subnet. CloudSigma has this, AWS has most of it but few others do. Without this a true hybrid set-up is still lacking in their cloud solution.