Reliability vs Resilience: Understanding the Difference and Its Importance

Whenever I discuss reliability with customers and partners, I am reminded that despite differing goals and priorities, everyone ultimately wants their services to work as intended; customers want to operate online at their convenience, and providers want their customers to perform any task at any time.

This article is the first in a four‑part series on building resilient services. The series will cover: Reliability vs Resilience – what the difference is and why it matters. Common Threats to Reliability – using the DIAL mnemonic (Discover, Identify, Authorize/Authenticate, Limit/Delay) to brainstorm potential failure points and support resilience modeling and analysis (RMA). Reliability‑Enhancing Techniques (D & A) – exploring design improvements related to discovery and authentication. Reliability‑Enhancing Techniques (I & L) – exploring design improvements related to errors and limits.

My goal is to dive into how Microsoft views reliability and the processes and technologies we use to improve the reliability of customer services.

So, what is reliability? The most common answer from customers and partners is consistent performance, speed, and availability – perhaps most importantly, resilience. We all agree that for a system or service to be reliable, users must trust that "it will work correctly."

The IEEE Reliability Society defines reliability engineering as “a design engineering discipline that applies scientific knowledge to ensure a system performs its intended function in a given environment for a required period of time, including the ability to test and support the system throughout its lifecycle.” For software, reliability is defined as “the probability that software will run without failure for a specified period of time in a specific environment.”

A reliable cloud service essentially runs as designed, for the expected duration, and from any location the customer connects to. This does not mean every component must operate perfectly 100% of the time; that nuance leads to the distinction between reliability and resilience.

Reliability is the result that cloud service providers aim for – it is the outcome. Resilience is the ability of a cloud‑based service to withstand certain types of failures while still appearing to operate normally from the customer’s perspective. In other words, reliability is the result, and resilience is the means to achieve that result.

The key takeaway is to consider resilience at every stage of the software development lifecycle and to design and build services with resilience in mind.