Making the Right Decisions for Your Serverless Architecture
summary
A working URL shortener sits behind an Express front end on App Engine, with two Cloud Functions (createShortlink, getShortlink) that validate and write to a locked-down DB; a tiny Cloud Run service serves 404s using a Docker image (fortune + cowsay + ncat) named fortune-telling-cow. Deployment flow uses Docker → GCR, gcloud (beta) run deploy (Cloud Build optional), App Engine offers traffic splitting and managed SSL, Cloud Functions are single-concurrency, Cloud Run (Knative) is portable and bills per 100ms.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:03What is serverless?
- 3:31Serverless compute options
- 3:41The Spectrum of Serverless
- 12:57App Engine Standard Environment
- 22:38Cloud Run
related talks
43mBuild and deploy a serverless web app on GCP
36mCI/CD in a Serverless World
50mA hitchhicker's guide to Serverless computing
36mGoogle Cloud Platform: Cloud Functions, App Engine vs Container Engine.
27mServerless Containers with Google Cloud Run
35mConvergence of Serverless APIs & Compute
38mGCP Serverless Updates
25mCloud Run, serverless containers in action
