Writing Greener Java Applications
summary
Quarkus experiments measure power with RAPL telemetry and convert instance load to carbon using region grids (ElectricityMaps); results show Quarkus on the JVM uses roughly half the carbon of a legacy framework and native Quarkus is only slightly better, not dramatically lower. Simple ops changes matter: a shutdown script cuts cloud costs by 30%, a 16,000-server audit finds 25% idle “zombies,” and choosing greener regions (Virginia runs on coal) or scheduling by time of day yields big, provable carbon wins.
AI-written summary · about
chapters (8)
- 0:00The impact of IT on climate
- 1:12Reasons for climate action
- 6:27Hosting and energy awareness
- 11:52Elasticity and light switch ops
- 17:43Software efficiency and language
- 21:40Quarkus and carbon experiments
- 33:22Optimizing native vs JVM
- 37:57The double win of sustainability
related talks
39mCreate an Eco-Friendly World with Green Software Engineering
42mLess waste, more joy, and a lot more green: How Quarkus makes Java better
31mCreate an eco-friendly world with Green Software Engineering
46mThe Efficiency Paradox: How to Save Yourself & the World
49mThe Future is 💚: A Journey through the Energy Efficient ..
50mEnergy Efficient Design Principles of Software Engineering
49mJava Particle Acceleration using Quarkus
52mQuarkus Supersonic Subatomic Java