Ever wondered if you could run your web application container on a serverless platform? Wait no further with the recent Google cloud run release it is already possible. You can get from 0 to a working serverless URL for a containerized app in no time. Till now there was nothing that married the goodness of serverless with container's ease. Cloud run also makes deploying new versions very easy with its web interface. This talk will be a run-through of deploying and running a simple nodejs app on google cloud run in a matter of minutes.
Presented at Serverless Days Sydney Conference and Serverless July 2019 Meetup.
● What is serverless? Why serverless?
● Containers and why use them
● Current serverless FAAS oﬀering
● Cloud Spectrum
● Google cloud run (Serverless + Containers = Bliss)
● Performance comparison (Serverless vs FAAS)
“ Serverless was ﬁrst used to describe
applications that signiﬁcantly or fully
incorporate third-party, cloud-hosted
applications and services, to manage
server-side logic and state - BAAS.
Mike Roberts, Symphonia
“ Serverless can also mean applications where
server-side logic is still written by the application
developer, but, unlike traditional architectures,
it’s run in stateless compute containers that are
event-triggered, ephemeral (may only last for
one invocation), and fully managed by a third
party. - FAAS.
Mike Roberts, Symphonia
Reasons to use Serverless
● Server management is not necessary
● Cost based on precise usage (by the second)
● Inherently scalable (load based autoscaling)
● Implicit high availability
● Quick deployments and updates (Functions)
● Faster to reach a working application (time to
Focus on your application (code), not the infrastructure
“ A container is a standard unit of
software that packages up code and all
its dependencies so the application runs
quickly and reliably from one computing
environment to another.
Control Ease / Abstraction
Cloud Spectrum - the sweet spot
Google Cloud Run
● Cloud Run is a managed compute platform that
automatically scales your stateless containers.
● Cloud Run is serverless: it abstracts away all
infrastructure management, so you can focus on
what matters most — building great
Cloud Run advantages
● No need to learn a new paradigm/framework
● Run any language/framework/binary -- as it runs
containers (not ﬁxed runtimes)
● Serverless and fully managed
○ Cloud Run on GKE can be self managed (Knative)
● Https URL out of the box (custom domains
● The Google Cloud toolset goodness :)
● Getting from 0 to working URL is relatively easy