Where's the Kaboom? There Was Supposed to Be an Earth-Shattering Kaboom!
summary
Operations teams are awful at retiring systems and should borrow demolition practices: treat removal as reverse engineering, require a written deconstruction plan, and prefer transparency, simplicity and a limited number of large components over many tiny ones. Demolition uses weeks of prep for rare implosions and follows last on first off stripping and the six S's (site, structure, skin, services, space plan, stuff) to expose lifespan friction points where to cut dependencies and reclaim materials. Microservices help bounded contexts but multiply connection overhead when trying to take an entire system down.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:02Disclaimer
- 4:10Are we ready
- 9:43Demolition vs Construction
- 10:57Professional Demolition
- 11:37Reverse Engineering
- 12:34Sustainable Deconstruction
- 14:07Design for Disassembly
- 14:23Making Disassembly Easier
- 18:21How Buildings Learn
- 18:39The Six Ss
- 20:31Constant Friction
- 20:56The Big Idea
- 22:03Conclusion
- 22:38Questions
related talks
37mY2K and Other Disappointing Disasters: How To Create Fizzle
24mHow to delete everything: The clean-slate approach to technical strategy
13mTen Ways to Doom Your DevSecOps
32mTales from the DevOps Transformation Trenches
01h 02mTools for simplified large scale systems
40mKill "Microservices" before its too late
15mIncident Ready: Chaos Engineer Your Incident Response
07mTen Ways to Doom Your DevOps