Serverless landscape beyond functions
summary
Argues that serverless now covers containers, orchestration and eventing, not just functions, and demonstrates a working pipeline: Eventarc triggers Workflows that call two Cloud Functions, an external math.js API and a Cloud Run container to produce resized, labeled and watermarked images (executions return "filter label resize watermark 200" and output files). Notes Cloud Run (Knative) supports concurrency 80, request time up to 60 minutes, minimal instances to avoid cold starts, and auto‑scale with soft limits (default max instances ~1000).
AI-written summary · about
chapters (5)
- 0:00Start
- 9:03Phases of Serverless Simple Functions
- 15:45Phases of Serverless Containers and serverless maturity
- 26:07Phases of Serverless Expansion and integration of serverless
- 42:27Serverless + Serverful You can combine Serverless orchestration and VM for best of both worlds 1. Containerize the long-running task sok can run anywhere 2. Plan to run the container on a compute Engine VM with no time
related talks
45mServerless landscape beyond functions
48mServerless beyond functions
42mServerless Landscape Beyond Functions
50mChoreography vs Orchestration in serverless microservices
29mServerless on Kubernetes: What We Learned From Customers
47mServerless Compute at the Heart of Your EDA
38mChoreography vs Orchestration in serverless microservices
01h 08mUsing AWS Lambda and Azure Functions to develop serverless applications
