Does Cloud Native Mean Container Native?
summary
Argues containers are necessary but not sufficient for cloud native and that cloud native means customers want fewer infrastructure chores not just container runtimes. Credits immutable infrastructure via overlay filesystems for DevOps gains, cites that 70% of images are insecure (scanners expose more than VMs did), and proposes CSP-side image patching using overlays plus metadata to avoid forcing small customers to rebuild. Notes container-native bare metal gives near‑bare‑metal performance, and lightweight VMs or microcontainers suit fast serverless functions.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:51What does Cloud Native mean
- 7:35The genesis of Cloud Native
- 9:07Image via overlay
- 16:44Customers
- 20:03Overlays
- 24:04The Problem
- 26:58Container Native Bare Metal
- 34:45Conclusions
- 37:13Questions
related talks
42mCloud Native Applications
53m(Mis)Understanding Cloud Native
51mWhat Is This Cloud Native Thing Anyway?
03mGoing (cloud) Native
55mWhat Does Cloud-native Mean Anyway?
14mCloud Native vs. Platform Native vs...
05mCloud native or cloud agnostic? The questions you need to ask
23mKeynote: A Brief History of the Cloud from Servers to VMs to Buildpacks to Cloud Native Containers
