Slide 1

Slide 1 text

Guillaume Laforge Google Cloud, Developer Advocate Serverless containers with Cloud Run @glaforge

Slide 2

Slide 2 text

Operational Model Programming Model No Infra Management Managed Security Pay only for usage Service-based Event-driven Open What is Serverless

Slide 3

Slide 3 text

Containers • Any language • Any library • Any binary • Ecosystem of base images .js .rb .go .py .sh … 0 1 0 1 0 0 1 1 1

Slide 4

Slide 4 text

Containers: an industry standard 100 75 50 25 Note Apr 13, 2017 Sep 24, 2017

Slide 5

Slide 5 text

Introducing Cloud Run Bringing serverless to containers

Slide 6

Slide 6 text

Cloud Run Container to production in seconds Natively Serverless One experience, where you want it

Slide 7

Slide 7 text

Code, build & run Demo #1

Slide 8

Slide 8 text

Scale Demo #2

Slide 9

Slide 9 text

Cloud Run on GKE Demo #3

Slide 10

Slide 10 text

Serverless containers, where you want them Cloud Run (fully managed) • Fully serverless • No cluster to manage • Pay for what you use Cloud Run on GKE • Serverless developer experience • Runs in your GKE cluster

Slide 11

Slide 11 text

Cloud Run: Pay-per-use CPU / Memory / Requests 100ms

Slide 12

Slide 12 text

Use cases Public • Website • API endpoint Private • Microservices • Asynchronous tasks • Mobile backend • Webhook

Slide 13

Slide 13 text

Serverless compute options Serverless functions Source-based HTTP and Events Cloud Functions Serverless applications Source-based HTTP and async App Engine Serverless HTTP workloads Containers HTTP and async Cloud Run

Slide 14

Slide 14 text

Thank you! Also: ● Cloud Run FAQ: github.com/ahmetb/cloud-run-faq ● Awesome Cloud Run: github.com/steren/awesome-cloudrun ● Anytime on StackOverflow with the google-cloud-run tag @glaforge

Slide 15

Slide 15 text

https://cloud.run or try our Qwiklab today at https://google.qwiklabs.com Get started @glaforge