Green Code on the Cloud: Integrating Sustainability into DevOps Practices
summary
Cloud workloads account for measurable energy use (about 1% of global electricity with IT emissions rising) and nearly half of cloud resources sit over‑provisioned. The practical path shown is measuring with the AWS Customer Carbon Footprint Tool, cleaning unused data and backups, adopting autoscaling/serverless and regional placement, and shrinking CI builds and tests. A case study reports 40% cost reduction, 98% lower wait time, 26% faster runtime and a 99% carbon footprint reduction after optimizations.
AI-written summary · about
chapters (20)
- 0:00Introduction to Green Code
- 1:06Speaker background
- 2:12Climate impact of tech
- 3:37Why cloud sustainability matters
- 4:19Cloud’s environmental footprint
- 5:24Digital waste and inefficiency
- 6:29How data centers consume energy
- 7:36Cloud providers’ carbon goals
- 8:23AWS sustainability initiatives
- 10:34Introducing Dev GreenOps
- 11:16Changing culture for sustainability
- 11:57Measuring environmental impact
- 13:05Key metrics for green coding
- 13:48What is green coding
- 14:52Practical green coding steps
- 15:34Optimizing cloud resources
- 16:16Efficient build and deploy
- 17:01Case study: Baker Hughes
- 17:45Benefits of green DevOps
- 18:07Key takeaways and next steps
related talks
16mGreen Code: Transforming DevOps for a Sustainable Future
41mGo Green: Reducing Emissions, Costs & Greenwashing
31mBridging Product and Engineering for a Greener Future: Embedding Sustainability into Software Teams
27mDevGreenOps
50mCarbon-Aware Computing: Measuring and Reducing the Carbon Intensity of Software
55mCode that Won't Heat the Planet: Engineering Sustainable Software for a Better Future
12mFeeling the squeeze? A sustainable solution for busy teams
28mSustainability and Cloud Native: Strategies for a Green Future