The circle of life: lessons learned from killing services
summary
Services accumulate hidden costs and risks: GDPR fines reach £8.7m or 2% of turnover, cloud emissions already hit 2.1–3.9% of global CO2 (projected to 14% by 2040), Volkswagen stores 30,000 unused cars, Thomas Cook forces 150,000-person repatriation, startups leave £70,000 cloud bills. Practical fixes: include end scenarios at kickoff, build off‑boarding and data retention plans, design components so they can turn it off if unused, practice retiring small features to make big shutdowns manageable.
AI-written summary · about
chapters (8)
- 0:00Killing services intro
- 1:04Why avoid closing services
- 6:01Cost of doing nothing on services
- 13:23Designing from service graveyards
- 20:10Learning from endings
- 26:51Building with endings
- 33:17Final thoughts
- 40:24Q&A
related talks
55mCode that Won't Heat the Planet: Engineering Sustainable Software for a Better Future
34mCloud Chaos and Microservices Mayhem
41mGo Green: Reducing Emissions, Costs & Greenwashing
31mThe irony of cloud cost-cutting: when saving money leads to losing money
31mBridging Product and Engineering for a Greener Future: Embedding Sustainability into Software Teams
47mCost optimization
41mPlanet sends an SOS – Taking Responsibility for our Carbon Footprint
40mAvoiding Pain When Operating in the Cloud