The differences between microservices and containers
summary
Containers work on laptops but break assumptions in production: machine-centric monitoring, log access and troubleshooting need reworking, and stateless 12‑factor apps still require stateful backing services. Claims include using CI/CD and blue-green deployments to reduce risk, and running real‑time pipelines with the SMACK: Spark Mesos Cassandra Kafka stack rather than siloed one‑app‑per‑server deployments. Solution is a portable platform that automates operations like a public cloud while avoiding vendor lock‑in, offered as open‑source DC/OS and an enterprise edition, with elastic scaling and FaaS integrations.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:15Problems with containers
- 1:47Challenges with containers
- 2:05Microservices in containers
- 2:41Cloud native
- 3:11Deploys
- 3:42Risks and opportunities
- 4:49Realtime streaming data
- 6:40Public cloud
- 8:19Whats next
related talks
23mMicroservices and containers
01h 04mDeploying and Scaling Microservices
45mContinuously delivering containerized, highly available microservices
37mHow the hell do I run my microservices in production, and will it scale
37mKnee Deep in Microservices
47mIt is not just Microservices
48mA journey to micro-services on Mesos
28mHow the hell do I run my microservices in production, and will it scale?