Immutable infrastructure from containers to serverless
summary
Argues that containers do not guarantee immutable infrastructure and gives a measured claim that 60% of Docker Hub images violate immutability, tracing the gap to missing enforcement in container tooling and the kernel primitives — namespaces and cgroups — beneath the syscall interface. Compares VMs, containers and serverless, quantifies scaling jumps (containers are 10–100× denser than VMs) and predicts orchestrators must handle 50,000–100,000 scriptlets with tiny footprints to make serverless practical.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:02Physical systems to containers
- 2:46Immutable infrastructure assumptions
- 4:34Microservices trends
- 6:58Serverless evolution
- 9:45Serverless scalability
related talks
51mWho needs containers in a serverless world?
35mContainer vs. Serverless: The Good, the Bad and the Ugly
43mContainers Change Everything
17m99 Problems But a Container Ain’t One: Forget Serverless, Let’s Talk Containerless Development
56mContainers and the Cloud: Do You Need Another Virtual Environment?
44mServerless and containers are coming together: an AWS perspective
47mContainers - the little Linux feature revolutionizing apps
45mDoes Cloud Native Mean Container Native?