The good and the bad of Google Cloud Run

Click for: original source

Ben Kehoe wrote a blog post which is a general critique of Cloud Run relative to FaaS and managed API services – and how this is different from AWS Lambda.

Google’ s Cloud Run allows you to hand over a container image with a web server inside, and specify some combination of memory/CPU resources and allowed concurrency. The logic inside your container must be stateless.

Cloud Run then takes care of creating an HTTP endpoint, receiving requests and routing them to containers, and making sure enough containers are running to handle the volume of requests. While your containers are handling requests, you are billed in 100 ms increments.

All of the web logic is inside your container; auth*, validation, error handling, the lot of it.

What is good about Cloud Run?

  • Very simple for people who are running containerized, stateless web servers
  • Better scaling and fine-grained billing
  • Dead simple to test locally (container)

What is bad about Cloud Run?

  • Serverless should focus mainly on business value (outsource everything else to managed services)
  • It is not FaaS

Find out more in this first overview of Cloud Run!

[Read More]

Tags cloud google serverless aws