# Reliability

### What is reliability? <a href="#what-is-reliability" id="what-is-reliability"></a>

**Reliability**, `R`, is the probability that the service will perform its functions for a specified time. `R` measures how the service performs under varying operating conditions.

We often use **mean time between failures (MTBF)** and **mean time to repair (MTTR)** as metrics to measure `R`.

<figure><img src="https://1055613405-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MlQzjDKRh_AaQvZflWz%2Fuploads%2F2XrYH20URtG0AOzlB5Cc%2FScreenshot%202023-08-20%20at%204.41.49%20AM.png?alt=media&#x26;token=59428589-9c1a-4a90-ab9e-436ef7d3c5d6" alt=""><figcaption></figcaption></figure>

(We strive for a higher MTBF value and a lower MTTR value.)

#### Reliability and availability <a href="#reliability-and-availability" id="reliability-and-availability"></a>

Reliability and availability are two important metrics to measure compliance of service to agreed-upon service level objectives (SLO).

The measurement of availability is driven by time loss, whereas the frequency and impact of failures drive the measure of reliability. Availability and reliability are essential because they enable the stakeholders to assess the health of the service.

Reliability (`R`) and availability (`A`) are two distinct concepts, but they are related. Mathematically, `A` is a function of `R`. This means that the value of `R` can change independently, and the value of `A` depends on `R`. Therefore, it’s possible to have situations where we have:

* low `A`, low `R`
* low `A`, high `R`
* high `A`, low `R`
* high `A`, high `R` (desirable)

<figure><img src="https://1055613405-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MlQzjDKRh_AaQvZflWz%2Fuploads%2FUj0tsF5RUijauncHL6Ju%2FScreenshot%202023-08-20%20at%204.42.33%20AM.png?alt=media&#x26;token=cc9e7ec0-987a-4c5e-82f6-96306d7536d6" alt=""><figcaption></figcaption></figure>
