Sustainable Azure - Tools & Patterns for Carbon Aware Cloud Applications
summary
Industry IT emissions account for about 4% of global CO2 roughly twice aviation and rising, and simple changes cut at least 40% of cloud emissions often up to 50–70%. Practical moves are turn off unused VMs, raise server utilization with containers and Kubernetes plus KEDA and the Carbon Aware KEDA operator, prefer serverless or container apps that scale to zero, use Front Door to route between low‑carbon backends, schedule batch work with Azure Batch and spot VMs, and use Goldilocks for right‑sizing.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:50Global carbon emissions
- 2:36Agenda
- 3:42Emissions
- 6:30Fields of Action
- 7:37Optimization
- 8:58Server Utilization
- 10:08Idle Gap
- 13:30Roadmap
- 14:35Measures
- 20:55Scaling
- 25:23How to scale
- 27:21Demo
- 30:05Dynamic load
- 33:55Front door
- 37:23Kubernetes
- 40:45Carbon Intensity
- 46:05Container Apps
- 49:28Azure Batch
- 52:25Demandshaping
related talks
16mHow to Save Money and Thus CO2 with Azure
51mTowards a Carbon-Aware Cloud
41mWriting Greener Software Even When You Are Stuck On-Prem
34mEmbracing Sustainability in Cloud-Native Ecosystems
32mGreenOps in the cloud
49mArchitecting for Sustainability: A Software Architects Guide to Green Software Keynote
55mToward a carbon-aware Cloud
36mArchitecting in the Cloud for Sustainability