Serverless containers with Knative and Cloud Run
summary
Shows that containers can run serverless with Knative serving & eventing and as a fully managed service on Cloud Run managed. Demonstrates concrete stack pieces: Istio gateway, Cloud Pub/Sub triggers, Cloud Storage notifications, Cloud Scheduler and write-to-firestore persistence. Walks a migration: Windows VM → Compute Engine → App Engine Flex → Cloud Run, then decomposes an ASP.NET monolith into reader, converter, web microservices that communicate via Pub/Sub and storage; deployment time drops from ~5–10 minutes to seconds and monthly cost falls from ~$20–30 to nearly free.
AI-written summary · about
chapters (27)
- 0:00Intro
- 2:22Service vs Stateless
- 4:55Why not have both
- 7:08What is Knative
- 9:23What does Knative do
- 10:12What is native serving
- 13:05Knative in Google Cloud
- 13:41Deploying an app on Knative
- 16:52Setting up a domain
- 17:05Configuration changes
- 22:19Eventing
- 26:08Namespace
- 26:29CTL
- 26:50Deployment
- 28:23Triggering events
- 29:33Cloud Run
- 33:24Cloud Run Demo
- 35:49Cloud Run in Google Cloud
- 37:17Private services
- 38:44Other use cases
- 39:56Example
- 41:25Summary
- 42:12The initial app
- 45:04The next stage
- 47:41The next stage of the app
- 53:26Breaking it down
- 58:14Lessons learnt
related talks
47mServerless with Knative
48mEvent-driven serverless architectures using Knative and Cloud Run.
42mManaging Modern Serverless Workloads using &
23mServerless with Knative
55mEvent-driven serverless architectures using Knative and Cloud Run
25mCloud Run, serverless containers in action
52mServerless with Knative
45mServerless with Knative