Cloud Run, serverless containers in action
summary
Cloud Run deploys containers to production in seconds, runs managed on Google Cloud or on GKE via Knative, and scales 1 to 0 with billing per 100ms and a current 15-minute request timeout (moving toward 1 hour). Containers must listen on port 8080, start within ~4 minutes, be stateless and avoid background CPU after requests. Demo builds a Micronaut app with a multi‑stage Dockerfile, pushes to Container Registry, deploys with gcloud, and handles Cloud Pub/Sub and Cloud Storage events; it supports 80 concurrent requests per instance.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:54Service
- 2:46Containers
- 3:00Containers are everywhere
- 4:00Cloud on several containers
- 4:20Cloud Run
- 6:27Google Cloud
- 8:04Use cases
- 8:46Container requirements
- 10:52Bidding
- 11:18Concurrency
- 11:35Billing
- 12:05Concurrent requests
- 13:10Google Cloud Console
- 13:39Hello Service
- 13:55Revisions
- 16:09Deployment
- 16:44Service accounts
- 17:12Service revision
- 19:13PubSub
- 19:37DataField
- 20:27Launch Logs
- 21:35Google Cloud Storage
- 21:54Uploading a file
- 23:33Conclusion
related talks
32mCloud Run, serverless containers in action
27mServerless Containers with Google Cloud Run
41mCloud Run Your Code
37mGoing Serverless with Google Cloud Run
01h 01mServerless containers with Knative and Cloud Run
30mGoing serverless with Cloud Run
42mManaging Modern Serverless Workloads using &
42mNew serverless solutions on Google Cloud for functions, apps and containers