iwantcoding.com
🔥 Daily 👥 Rooms 🏆 Top Log in Sign up
Next »

14.3 Sustainable Cloud

A sustainable cloud strategy reduces money spent and carbon emitted at the same time. The levers - right-sizing, scheduling, region choice, architecture - are well understood and measurable. This lesson summarises the practical wins.

The Big Levers

LeverCarbon WinCost WinEffort
Right-size computeHighHighLow
Stop non-prod off-hoursMediumHighLow
Use spot / preemptibleMediumVery highMedium
Pick low-carbon regionHighNeutralLow
Refactor to serverlessMediumVariableHigh
Adopt Arm / GravitonMediumMediumMedium
Storage tiering (hot to cold)LowHighLow
Right-size network egressLowHighMedium

Measuring Cloud Carbon

ProviderToolWhat It Reports
AWSCustomer Carbon Footprint TooltCO2e by service, region, month
AzureEmissions Impact DashboardScope 1-3 by service
GCPCarbon FootprintgCO2e by region and project
Multi-cloudCloud Carbon Footprint (OSS)Estimates across AWS, GCP, Azure

Quick Patterns That Pay Off

  1. Tag every workload with `owner`, `cost-center`, and `environment` from day one.
  2. Set a `sunset-date` tag on every non-prod resource - automation deletes when overdue.
  3. Default to **Singapore, Tokyo or Sydney** for PH workloads only when latency justifies it; consider regions with cleaner grids when the customer is global.
  4. Move logs older than 30 days to cold tier; archive at 90; delete at retention end.
  5. Treat unused volumes, idle load balancers, and orphan public IPs as monthly cleanup targets - they are the silent budget killers.

Sustainable Architecture Mindset

Old DefaultNew Default
Provision for peakAutoscale or burst
Always-on dev/testSchedule off-hours
Monolithic DB clusterRight-sized clusters per workload
Generic x86 SKUsLatest gen + Arm where supported
Keep all logs foreverRetain only what is required

Discussion

Loading…

Next »