Containers as an enabler for microservices and what it means for our industry
summary
Argument: containers package application plus libraries into immutable images so teams build once and move them unchanged through environments, with Docker and the OCI image spec as the single currency. Runtime control comes from cgroups and namespaces and orchestration adds rollbacks autoscaling and canaries via Kubernetes orchestration or Swarm. Expect developer iteration to shrink from 20–30 minute VM build times to image pulls; target microservices at ~1–2k LOC not >5k. Real-world gain: one bank runs 20% of apps on 3% of estate.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:58The classic problem
- 4:20Devs are creative
- 5:30Containers
- 9:15Container packaging
- 9:50Containers as a single currency
- 11:10Demo
- 13:35Microservices as containers
- 16:15Container orchestration
- 18:30Software collections
- 21:10Release cycles
related talks
30mContainers and Next Gen Infrastructure Ecosystem
23mMicroservices and containers
31mMicroservices and Docker at Scale: the PB&J of Modern Application Delivery
10mThe differences between microservices and containers
45mContinuously delivering containerized, highly available microservices
20mMicroservices in the future
36mFrom VMs to Containers: Decompose and Migrate Old Applications
01h 04mDeploying and Scaling Microservices