How the hell do I run my microservices in production, and will it scale
summary
Clinic-ready advice: use Dockerfiles built and tested locally, produce slim secure speedy stable images, and treat images as immutable artifacts; avoid running stateful databases in containers (don't run databases in containers). The platform reality states: company manages 700 brokers over 4,000 servers and finds ~60% of customers run a monolith-inside-container, ~30% API-first, ~7% splitting to services and ~3% on Mesos experiments. Production requires orchestration, discovery, monitoring, logging, backup and clear lifecycle/versioning.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:35The Hero's Journey
- 11:10The Containerization Machine
- 11:34Introduction
- 12:42How To Design Your Images in Containers
related talks
28mHow the hell do I run my microservices in production, and will it scale?
36mDocker Inside/Out
45mContinuously delivering containerized, highly available microservices
10mThe differences between microservices and containers
31mMicroservices and Docker at Scale: the PB&J of Modern Application Delivery
31mDockerized app in production? YES WE CAN!!
01h 04mDeploying and Scaling Microservices
51mDeploying And Scaling Microservices