5 Tricks To Make Your Apps Greener, Cheaper & Nicer
summary
Gives five concrete levers: pick region and time using ElectricityMap (Virginia is notably coal‑heavy), adopt “light‑switch Ops” to stop zombie and underutilized instances (2017 study: ~25% idle, 29% under 5% utilization; $26.6B wasted in cloud always‑on spend), use the Vroom model (shorter runtime ≈ lower energy), apply the economic model (cost drops track carbon drops), and shows measured results with Quarkus (20‑day load tests, T2 micro vs T2 medium, Quarkus on JVM halves carbon vs an alternative; native has throughput tradeoffs).
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:27It's all of us
- 5:24Be a solutionist
- 7:43Trick 1
- 19:00Trick 2
- 26:09Trick 3
- 27:09Trick 4
- 33:20Trick 5
- 34:29Conclusion
- 40:28Summary
- 41:10Outro
related talks
47mLean Mean Green Machines - Architecting for a Greener Future
34mSustainable Software Engineering, Building Carbon-Efficient Applications
41mGo Green: Reducing Emissions, Costs & Greenwashing
16mGreen Code: Transforming DevOps for a Sustainable Future
55mCode that Won't Heat the Planet: Engineering Sustainable Software for a Better Future
19mGreen Code on the Cloud: Integrating Sustainability into DevOps Practices
42mFive (and a half) Cool Things You Can Do With Quarkus
50mCarbon-Aware Computing: Measuring and Reducing the Carbon Intensity of Software