The state of Green Washing
summary
Claims that ICT rivals aviation and cement in emissions and that global warming recently crossed 1.5°C motivate concrete actions: use carbender and Kepler to measure per-application power, apply the Software Carbon Intensity (SEI) formula (example: a Prometheus three-node stack ~4.01 g CO2eq/w·h, ~400 km car per year), and prefer architectures that scale to zero (WebAssembly examples: 1–2 MB, ~50 ms startup). Avoid blind optimizations like blanket ARM migration; energy forecasts range from ~4% to ~20% of global demand by 2030.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:03Why sustainability matters now
- 2:29ICT’s environmental impact compared to industries
- 4:15Carbon footprint paradox in ICT
- 6:22Kubernetes for sustainability
- 7:27CO2 scopes in cloud
- 8:31Optimizing container images
- 10:16Scheduling by carbon data
- 11:40Top-down green washing reduction
- 13:03Energy monitoring tools
- 14:51Matching apps to energy mix
- 15:56Hardware choices at Google Cloud
- 16:39Architecture for sustainability
- 18:04Data mesh unsustainability
- 19:30Language efficiency impact
- 20:57Software Carbon Intensity
- 22:41Embodied carbon of servers
- 24:07SEI for optimization
- 24:49Sustainable CI/CD pipelines
- 26:15Myths on time shifting
- 26:57Old vs. new hardware paradox
- 28:21Q&A
related talks
55mCode that Won't Heat the Planet: Engineering Sustainable Software for a Better Future
57mSustainable Green Software development
46mMaking Software & Data Architectures Sustainable
41mWriting Greener Software Even When You Are Stuck On-Prem
43mGreen Software – How To Make Our Applications Carbon Aware?
38mGreen software: How can tech contribute to worldwide sustainability effort?
28mSustainable IT : Connect the Dots to a Greener Future
01h 47mGreen computing