Se7en Deployment Sins
summary
Seven concrete deployment pitfalls with real examples and fixes: warns that tiny utilities like left-pad (eleven lines) once broke large parts of npm; recommends use explicit image versions because relying on latest can silently upgrade Elasticsearch nodes and kill a cluster; urges central logging and distributed tracing, never committing secrets (exposed AWS keys lead to crypto‑mining), and not running containers as root; critiques microservices-for-everything, Jenkins fragility, Docker-compose pitfalls (docker-compose -v removes volumes).
AI-written summary · about
chapters (14)
- 0:00Deployment Sins
- 2:38Memory, Disk, Network
- 9:04Don't forget - having legacy software is often a sign of success. Your business was successful to last long enough for your software to become legacy. - 929622273065136130
- 10:50Sun Microsystems 8 fallacies of distributed computing
- 11:14Jeff Hodges Notes on Distributed Systems for Young Bloods on-distributed-systems-for-young-bloods
- 21:58Boss by Red Hat
- 23:22Continuous Delivery CD Manual production deployment
- 23:33Continuous Deployment CD Automated production deployment
- 27:03Continuous life or death cycle?
- 27:16Jenkins
- 29:45Separate code and config
- 36:57New dependencies of your artifacts JVM and base image
- 48:07DevOps is not a technology
- 50:36Questions? Confessions? @xeraa
related talks
49mSe7en Deployment Sins
05mSeven Deadly Sins of Software Deployment
38mAdventures in Cloud Security: What DevOps Can Learn from a Security Engineer
14mHow to Not-Mess-Up Production
07mDon't Go There! Horrible Devops Security Blunders
29mDevSecOps: Five Common Mistakes
52mThe Complete Guide to Secret Hygiene for Java and Cloud-Native Engineers
46mApplication security from start to finish