Half your infrastructure may exist just in case.
Teams over-deliver on availability targets with hot standbys and full duplicates, doubling infrastructure for downtime the business could tolerate.
The Green Software Foundation suggests matching uptime targets to what the business really needs. GreenCode draws on these patterns when it checks software.
GreenCode helps tackle this by mining a running estate, rebuilding it as infrastructure as code and tracing energy and CO2e to the services that cause it, including services barely running at all. More on this.
Half your infrastructure may exist just in case. Teams often aim higher on uptime than the business asked for. Hot standbys and full copies wait for a failure that rarely comes. That can double your infrastructure, for downtime the business could live with. Every extra nine of uptime needs machines that run, and draw power. Whether they are used or not. Here is the fix you can use today. First, agree uptime targets with the business, for each service. Next, design each service to its own target. Not to the target of your most critical service. Then check your standby capacity against your real incident history. Tools like Cloud Carbon Footprint estimate its energy and emissions from your billing data. The Green Software Foundation suggests matching uptime targets to what the business really needs. GreenCode draws on these patterns when it checks software. GreenCode helps tackle this by tracing energy to the services that cause it. It rebuilds your running systems as code, and shows services that barely run. That was GreenCode Tech Tip number forty-eight. Follow for the next tip, and find more on greencode.ai/tech-tips.
Share this