---
title: "Tech Tip #48: Don't buy availability you don't need"
description: "Half your infrastructure may exist just in case."
url: https://greencode.ai/tech-tips/48-dont-buy-availability-you-dont-need/
---

# Tech Tip #48: Don't buy availability you don't need

**Half your infrastructure may exist just in case.**

[Watch the video](https://media.greencode.ai/shorts/dont-buy-availability-you-dont-need-8caf4cc064c8.mp4)

Video created by [explainapaper.com](https://explainapaper.com/?utm_source=greencode.ai&utm_medium=film&utm_campaign=made-by)

### The problem

Teams over-deliver on availability targets with hot standbys and full duplicates, doubling infrastructure for downtime the business could tolerate.

### The fix you can use today

- Agree availability targets with the business, per service.
- Design each service to its target, not to the most critical one's.
- Review standby capacity against real incident history.

The Green Software Foundation suggests matching uptime targets to what the business really needs. GreenCode draws on these patterns when it checks software.

### Tools that help

- [Cloud Carbon Footprint](https://www.cloudcarbonfootprint.org/?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode): estimates the energy and emissions of AWS, Azure and Google Cloud usage from billing and usage data

### How GreenCode helps

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](https://greencode.ai/feature/infrastructure-carbon-footprint-assessment/).

### Tags

#resilience#cost#governance

### Sources

- [Green Software Foundation, Green Software Patterns: Match your service level objectives to business needs](https://github.com/Green-Software-Foundation/patterns/blob/main/docs/requirements/match-slo.md?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode)
- [Microsoft, Azure Well-Architected sustainability (Reliability): right-size failover environments, review replication and backups](https://learn.microsoft.com/en-us/azure/well-architected/sustainability/sustainability-reliability-recommendations?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode)
- [Microsoft, Azure Well-Architected sustainability (Reliability): align resiliency to business continuity requirements, question multi-region](https://learn.microsoft.com/en-us/azure/well-architected/sustainability/sustainability-reliability-recommendations?utm_source=greencode.ai&utm_medium=referral&utm_campaign=greencode)
- [W3C, Web Sustainability Guidelines: favour standalone over multi-zone when requirements allow; provision for average load](https://www.w3.org/TR/web-sustainability-guidelines/#lowest-requirements)

[All GreenCode Tech Tips](https://greencode.ai/tech-tips/)

#### Key Facts

- Tip **#48**
- For **CTOs and technical leads**
- Category **Strategy, reporting and procurement**
- Format **short video**
![GreenCode](https://greencode.ai/wp-content/uploads/2024/12/greencode-logo-website-small-colours-2.webp)

Want this checked on your own system? Talk to the GreenCode team.

[Get in touch](https://greencode.ai/contact/)
