Microservices and Docker at Scale: the PB&J of Modern Application Delivery
summary
Explains why Docker pairs with microservices for faster releases and lower runtime overhead, and recommends concrete practices for enterprise rollout: one pipeline per service, automated image scanning into a registry, and container-native monitoring with request correlation IDs. Covers orchestration, autoscaling, DR patterns, hybrid integration with legacy apps, state and volume strategies, and governance to stop shadow IT. Advises rigorous automated testing, service discovery, and using immutable images to simplify operations and improve security.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:17Why Microservices?
- 8:36Why Microservices in Containers?
- 11:38Challenges Common to Both • Complex tools for solving complex problems
- 14:43Microservices Can Be Challenging • Distributed Systems Are Hard
- 23:19Challenges at Enterprise Scale
- 24:53Common Best Practices
related talks
37mKnee Deep in Microservices
45mContinuously delivering containerized, highly available microservices
53mMicroservices Lifecycle Through Docker an CD
01h 04mDeploying and Scaling Microservices
28mHow the hell do I run my microservices in production, and will it scale?
49mMicroservices: An unexpected Journey
51mDeploying And Scaling Microservices
37mHow the hell do I run my microservices in production, and will it scale