Urgent.News

What's breaking now, across thousands of outlets.

Tech

Five Nines Availability Architecture: What Single-Region, Multi-Region, and Multi-Cloud Designs Can Deliver

99.999% availability allows about 5 minutes 15 seconds of downtime per year, or about 26 seconds per month. That budget includes every failed deploy, certificate expiry, DNS misconfiguration, and provider incident in the request path. One regional outage lasting an hour consumes more than 11 years of five-nines budget. This guide explains which architecture tiers can reach that number, which…

The five nines availability architecture provides extremely high levels of uptime, with a budget of about 26 seconds of downtime per month. However, achieving this requires a multi-cloud, multi-region design. In a single region on a single cloud, reaching five nines is not possible due to the cumulative impact of various failures such as deploy issues, certificate expiry, DNS misconfigurations, and provider incidents. For example, an hour-long outage in a single region consumes over 11 years of the five-nines budget.

Three-tier architectures like multi-AZ single-region designs can achieve three to four nines of availability. However, same-provider multi-region designs can reach four nines, while cross-provider multi-region designs are the only tier capable of attaining five nines. This is because cross-cloud replication layers and independent failure domains help maintain availability even when provider-specific outages occur.

In a multi-AZ single-region single-cloud design, the achievable uptime ranges from 99.9% to 99.99%, equivalent to three to four nines. While this tier handles hardware and data center failures well, it cannot absorb a regional service failure. The AWS DR whitepaper states that for workloads where disaster means losing one physical data center, backup and restore may be sufficient. However, if the definition of disaster includes losing a region, the availability budget will be quickly exhausted.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Mid-air flips and side nozzles: selling flight without rewriting the hitbox

In a landscape browser runner, a jump that only changes Y position feels like a hop. A flip that rotates the car, keeps underbody jets lit, and throws mist from the side nozzles feels like flight.

  • Players use A/D for lane changes, W/Spacebar for jump-flip, S for ground roll, Shift for boosting.
  • Mid-air flip is intentional, not hover, with fixed camera and timing.
  • Side nozzles are visual markers, collision detection separate from effects.

Kubernetes: presupuestos de tiempo para correo en CI

Un pipeline de CI puede tardar varios minutos y aun así terminar con un mensaje poco útil: “no llegó el correo”. En una prueba que usa un disposable email address , ese fallo no dice si la aplicación…

  • Each test stage should have a defined time budget for diagnosis
  • Collect four signals: worker restarts, pod age, queue depth, correlation
  • Use unique addresses per execution to isolate inbox for verification

More from Thursday 22 October →