DevGreenOps
summary
Links between FridayForFuture and DevOps lead to concrete steps: use cloud provider carbon calculators to measure cloud carbon footprint per region, compare energy mixes (Microsoft, Google, AWS show big differences), attribute emissions to specific components like load balancers, container registries and website traffic, and cut unnecessary CI/CD runs to reduce pipeline runs. The talk shows surprising region-level differences, gives a checklist for measuring emissions in existing pipelines, and suggests choosing greener regions or providers as a deploy-time decision.
AI-written summary · about
chapters (9)
- 0:00DevGreenOps intro
- 3:15Climate change impact
- 8:08Carbon emissions in IT
- 13:00Measuring web footprint
- 17:22Cloud carbon efficiency
- 20:24Carbon footprint examples
- 23:41Tracking emissions tools
- 25:10Tech carbon partnerships
- 26:45Q&A
related talks
12mFeeling the squeeze? A sustainable solution for busy teams
19mGreen Code on the Cloud: Integrating Sustainability into DevOps Practices
24mGreen DevOps: Reducing the Environmental Footprint with DevOps
42mUndertaking a GreenOps Approach in the Public Cloud
41mWriting Greener Software Even When You Are Stuck On-Prem
16mGreen Code: Transforming DevOps for a Sustainable Future
25mHow to measure ICT carbon footprint? A quick guide to GreenOps toolkit
31mBridging Product and Engineering for a Greener Future: Embedding Sustainability into Software Teams