99.9% availability still allows for 43 minutes of downtime

Suppose an application promises to be available 99.9% of the time over the course of a month. That number seems extraordinarily high, but it leaves room for about 43 minutes of unavailability over thirty days. That margin is the error budget: the amount of failure the service can afford before violating the agreed-upon reliability level. The usual instinct would be to pursue 100%. However, aiming for absolute availability can be unnecessarily expensive and, in some cases, counterproductive. Every additional layer of redundancy, every slower deployment, and every restriction on changing the product comes at a cost. A music service can tolerate a brief interruption much better than a system that coordinates emergency response. That is why a good objective does not ask, “Can we achieve five nines?”—that famous 99.999% availability—but rather, “What is the minimum level that truly protects our users?”

Full episode: https://youtu.be/f2M_JlRwXpY

🤖 AI-generated content: the script, voices, and images in this episode were produced using artificial intelligence tools.

#Shorts