Google recently announced Cloud Run, a new serverless compute platform for containerized apps that offers built-in portability. It’s meant to help solve some of the biggest pain points for developers when it comes to working with serverless offerings. To learn more about the tool and what it provides, here’s a rundown.
About Cloud Run
Cloud Run is now available in beta. It allows you to run stateless HTTP-driven containers while it takes care of all the infrastructure management tasks like provisioning, configuring, scaling, and server management. It also scales automatically depending on traffic to help users keep costs under control.
Traditionally, serverless tools have presented some challenges for users, like constrained runtime support and vendors that are locked in. Basically, developers had to choose whether or not the speed and ease of serverless was worth losing that flexibility and portability that comes with containers. Cloud Run is meant to help you solve that problem, giving developers what it calls “the best of both worlds.”
You also have the option of customizing your Cloud Run experience using third party tools and APIs. Here are a couple of the options that users are taking advantage of.
Cloud Run is based on an open API and runtime environment called Knative. Knative lets you run serverless workloads that are fully managed on GCP or your own clusters from anywhere. So if you want to run workloads on-premises or across multiple cloud environments. You can use Knative in your own clusters or migrate that data to Cloud Run.
Cloud Run is also available on GKE, allowing you to access all the benefits of both platforms at once. This means you can deploy stateless HTTP service and run serverless workloads right on your existing GKE clusters. This also allows you to take advantage of custom machine types, Compute Engine networks, and side-by-side workloads in the same cluster.
Featured image: Google