Availability

Availability is the fraction of time a system is operational and reachable by its users, expressed as a percentage. If a service is up for 999 out of every 1000 minutes, it has 99.9% availability. People talk about it in "nines" because each extra nine is roughly a 10x reduction in allowed downtime, and each one is dramatically harder and more expensive to reach.

The math is simple. Availability equals uptime divided by total time. Over a 365 day year that is 525,600 minutes. So 99% lets you be down for about 3.65 days, 99.9% for about 8.77 hours, 99.99% for about 52.6 minutes, and 99.999% ("five nines") for about 5.26 minutes. A cloud provider's SLA of 99.95% means they promise no more than about 4.4 hours of downtime per year, or they owe you service credits.

Availability is not the same as reliability or durability. Reliability is about whether the system behaves correctly when it is up. Durability is about whether your stored data survives. A database can be 99.999% durable (it almost never loses data) but only 99.9% available (it sometimes refuses connections during a failover).

The core lever is removing single points of failure through redundancy. Instead of one web server you run several behind a load balancer, so one crashing does not take the site down. Instead of one database you keep a replica that can be promoted if the primary dies. The system stays available as long as at least one healthy copy of each component exists.

Redundancy only helps if failures are detected fast and traffic is rerouted automatically. Health checks ping each instance every few seconds, and the load balancer stops sending traffic to anything that fails them. Failover promotes a standby to take over a dead primary. The time this takes, often called recovery time, directly eats into your availability budget.

There is a useful rule for combining components. When parts are in series, meaning all of them must work, you multiply their availabilities, so two 99.9% services chained together give only 99.8%. When parts are redundant, meaning any one is enough, the combined system is far more available than either alone. This is why a system with many dependencies needs each one to be very reliable, and why teams spread copies across separate availability zones and regions so one data center outage cannot take everything down.

More availability is not free, and chasing nines you do not need wastes money and engineering time. The right target comes from the business. A payment system or hospital records system may justify five nines. An internal analytics dashboard is fine at three nines. The CAP theorem also forces a choice: during a network partition you can keep serving requests (stay available) or refuse them to stay strongly consistent, but not both.

Each extra nine roughly multiplies cost. Going from 99.9% to 99.99% often means multi-region deployment, automated failover, on-call rotations, chaos testing, and far more operational discipline. Going to five nines can mean active-active across regions with no manual steps anywhere in the recovery path, because even a few minutes of human reaction time blows the budget.

Most outages are not caused by hardware. They come from bad deploys, configuration mistakes, and dependency failures. So beyond redundancy, real availability work includes gradual rollouts, fast rollback, circuit breakers, rate limiting, and graceful degradation where the system serves a reduced experience instead of failing completely.

Consider an online store running in AWS. A single EC2 instance running both the app and the database might give you 99% availability, which is about 3.65 days of downtime a year and unacceptable for a shop.

Now spread it out. Run the app on three instances across three availability zones behind an Application Load Balancer, and use a managed database like RDS with a standby in a second zone for automatic failover. A single instance crash is invisible to customers because the load balancer reroutes traffic in seconds, and a database failure promotes the standby in a minute or two. This setup commonly reaches 99.95% to 99.99%.

If the business then needs to survive an entire AWS region going down, you replicate the whole stack into a second region with DNS-based or global load balancing that shifts traffic when the primary region fails health checks. That added complexity is what buys the jump toward five nines, and it is only worth it if a regional outage would genuinely cost more than the engineering and infrastructure it takes to defend against one.