Who needs containers in a serverless world?
summary
Argues that serverless is really functions as a service — small, event‑driven code that scales to zero and charges per invocation — with AWS Lambda, Google, Azure and open alternatives like OpenWhisk. Notes tooling: Docker, Kubernetes/OpenShift, source‑to‑image, draft, Apex and OC cluster up (OpenShift local needs ~9GB). Claims containers remain more versatile (example: a 3.5GB Java image) and production‑mature, while serverless tooling is promising but still early.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 8:31Containers in infrastructure
- 10:22Serverless
- 14:58Service
- 21:13Providers
- 22:11Open Source
- 22:56Containers
- 24:46Developers workflow
- 34:49Summary
- 37:09Other considerations
- 40:03The mind shift
- 42:36Vaclavs quote
- 45:05Openshift
- 45:32OpenWhisk
- 46:18Wrapup
- 47:25Questions
related talks
44mServerless and containers are coming together: an AWS perspective
24mContainers vs Serverless from a DevOps standpoint
01h 00mMicroservices and Serverless
41mContainers or Serverless Functions - When to choose what?
44mThe container inside serverless
45mServerless landscape beyond functions
53mServerless is the Abstraction We Deserve
32mEmbracing Serverless Ops