Docker in Production
summary
A Casual‑gaming platform (betterdeal.de) runs Docker in production across two hosts with 14 containers handling frontend, auth, scoring, logging and persistence. Deployment uses a custom rollout tool (~800 LOC) that converts Compose‑like YAML into parameterized shell scripts; images mostly use latest, base rebuilds take ~40 minutes, and operations rely on Docker restart, a private registry, health checks and centralized logs (logspout → aggregation).
AI-written summary · about
chapters (21)
- 0:00Introduction
- 5:28Docker in production
- 9:42Casual Gaming Platform example
- 13:17Architecture and stack
- 16:30Orchestration and deployment
- 22:42Container design
- 27:28Container configuration
- 31:45Networking and security
- 33:02Data persistence challenges
- 36:54Local dev and testing
- 37:37Image registry and builds
- 41:14Image layers optimization
- 44:17Release management
- 51:49Image tracking
- 55:32Monitoring and logging
- 58:58Scaling and robustness
- 1:00:01Container performance
- 1:02:13Data lifecycle management
- 1:04:08Containers vs VMs
- 1:05:35Automation and CI/CD
- 1:07:23Summary
related talks
36mDocker Inside/Out
01h 04mPreparing your Dockerised Application for Production
31mDockerized app in production? YES WE CAN!!
40mGoes Beyond CI to Production Scale PaaS with Docker
43mServer Infrastructure for Rails in 2016
51mProduction level Docker
47mPatterns for Docker Success
23m12 Factor Frontend Apps through Dockerization