Se7en Deployment Sins
summary
Seven concrete deployment mistakes with examples and fixes: adding huge dependency trees (AWS SDK was split because pulls were massive), containers that balloon past 500+ MB and run as root, fragile Jenkins setups and CI that stays perpetually red, and overzealous microservice splits that create a distributed big ball of mud. Practical rules: don't commit secrets, avoid ambiguous no latest tag images, enforce centralized logging with correlation IDs, and automate infrastructure so pets become cattle — these practices reduce outages and toil.
AI-written summary · about
chapters (17)
- 0:00Start
- 1:29Memory, Disk, Network
- 5:36Sun Microsystems 8 fallacies of distributed computing
- 6:22Systems for Young
- 15:30Continuous Integration CI Build and test every push
- 15:42Continuous Delivery CD Manual production deployment
- 15:54Continuous Deployment CD Automated production deployment
- 18:38Continuous life or death cycle?
- 20:09Separate code and config
- 20:35Do not commit secrets
- 24:47A container is just a process
- 36:27DevOps is not a technology
- 37:22Craft everything yourself!
- 37:51Infrastructure Pets vs Cattle
- 39:07Avoid Drift
- 40:32Log & Monitor
- 41:57Questions? Confessions? @xeraa
related talks
52mSe7en Deployment Sins
05mSeven Deadly Sins of Software Deployment
41mContinuous delivery in 10 easy mistakes
46mContinuous delivery antipatterns
38mAdventures in Cloud Security: What DevOps Can Learn from a Security Engineer
07mDon't Go There! Horrible Devops Security Blunders
32mPractical Tips & Tricks for CI/CD Success
29mDevSecOps: Five Common Mistakes