Google Cloud Next: Cloud Run ushers in new age of serverless containers

Google Cloud Next 2019 press conference announcing Cloud Run

The cloud environment aims to provider greater developer choice without the vendor lock-in

Cloud Run, Google Cloud's latest serverless compute platform, has entered a beta phase and aims to combine the flexibility and portability of containers with the agility of serverless.

Revealed at Google Cloud Next 2019 in San Francisco, the Cloud Run environment will let developers build apps on a hybrid platform that also promises to be stateless, erasing the issue of vendor lock-in that's become a cause of concern for many.

With a serverless environment, developers need not worry about configuring the underlying infrastructure and how much resources they will need to power their applications. Cloud Run uses HTTP-driven containers and fully manages all the execution needs of the build, automatically scaling resources up or down within seconds, meaning that you'll only pay for the resources that you need.

"What's beautiful about the system is that you're paying by the hundred-millisecond for what you use only and it scales up horizontally to many, many thousands of cores in just a few seconds," said Oren Teich, director product management at Google Cloud.

It's already and being deployed by some of the world's biggest firms. Veolia, the waste management giant praises the ease and cost-effectiveness of the new environment.

"Cloud Run removes the barriers of managed platforms by giving us the freedom to run our custom workloads at lower cost on a fast, scalable, and fully managed infrastructure," said Hervé Dumas, group CTO at Veolia. "Our development team benefits from a great developer experience without limits and without having to worry about anything."

The Cloud Run environment can be used on its own or integrated with your company's existing Google Kubernetes Engine clusters; merging the two will also offer you some specific enhancements to your stack. This includes the option to run workloads side by side within the same cluster.

Using Cloud Run on Kubernetes grants access to Google's other Virtual Cloudsducts such as Custom Machine Types on its Compute Engine networks, which provides users with the ability to create scalable virtual machines tailored for each process that are configurable for optimal pricing.

Airbus Aerial, the aerospace company's satellite imagery arm is already using Cloud Run on Kubernetes to process and stream aerial images.

"With Cloud Run on GKE, we are able to run lots of compute operations for processing and streaming cloud-optimized aerial images into web maps without worrying about library dependencies, auto-scaling or latency issues," said Madhav Desetty, chief software architect at Airbus Aerial.

Cloud Run is also based on Google's Knative open API which lets users run workloads on Google Cloud Platform, on a Google Kubernetes Engine (GKE) cluster or on a company's own self-managed Kubernetes cluster. The underlying Knative API makes it easier for businesses to start on Cloud Run and then move to Cloud Run on GKE later on.

There are some operational constraints to Cloud Run which Teich detailed in a press conference. It runs at a maximum of 1Gb memory size instance, and you get a single core per instance, so it will scale horizontally rather than vertically. Each process must also respond to an HTTP 1.1 request in a maximum time of 15 minutes.

Sign up for our free newsletter