In Silicon Valley, Engineers Deploy-and-Tell: Stories About Dockerizing an Application
summary
A containerized monitoring pilot uses AWS ECS, Docker, Java, .NET and Node.js and proves that specifics matter: a prototype takes about three weeks, Node API runs as 12 Docker containers, and the surprise root causes are mundane — containers exit for lack of a long‑running process, the docker daemon isn’t accessible until the mount docker socket is mapped, and a bad EC2 Windows image breaks Hyper‑V. A live demo shows canary vs stable releases, errors concentrated in the West data center, and CI/CD integration with Jenkins for faster rollback.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:07Background Prototype
- 7:54Measure Performance
- 8:43Challenges Non-Tech
- 13:44Level SET Docker Fundamentals
- 16:42Tech Challenge 1
- 20:02Tech Challenge 3
- 32:53Part 3 - Up and Running Shorten the Feedback Loop
related talks
01h 06mSo many Docker platforms, so little time...
32mUsing Docker in test automation
01h 18mEmbracing Docker simplicity - while harnessing platform power
26mContainerization War Stories
27mThe Night of the Living Containers: Horror Stories from the DevOps World
41mContinuous Delivery with Docker Containers and Java EE
37mLessons learned from dockerizing complex Web Apps
42mCase Study – Arjuna Rivera
