reliability
The ability of a system to keep doing its job correctly, including recovering from failures, for as long as it is needed.
In more detail
Reliability combines availability, durability and the ability to recover from failures. It is usually improved by removing single points of failure, for example by spreading a workload across availability zones, and it often pulls against cost. Service level objectives turn reliability into a number a team can track.
Related terms
- availability — The share of time, or of requests, in which a service works for the people who need it, often written as a percentage such as 99.9 per cent.
- multi-AZ — Running a system in two or more availability zones, often as a primary plus a standby copy, so losing one zone does not take it down.
- backup and restore — Keeping recoverable copies of data from past points in time, and being able to bring them back.
- service level objective — A target for a service level indicator over a time window, such as 99.9 per cent of checkouts succeeding over 30 days.
- SRE — Site reliability engineering: Google's approach of running operations as a software engineering problem, with reliability targets, error budgets and limits on toil.
- error budget — The amount of failure an SLO allows over its window: one minus the target, for example 0.1 per cent of requests at 99.9 per cent.
Taught in
- A Retailer Moves To Azure In A Weekend — Microsoft Azure Fundamentals (AZ-900) Exam Prep
- Consumption Pricing And Serverless — Microsoft Azure Fundamentals (AZ-900) Exam Prep
- The Benefits, In Microsoft's Words — Microsoft Azure Fundamentals (AZ-900) Exam Prep
- Networking — Microsoft Azure Fundamentals (AZ-900) Exam Prep
- Monitoring: Advisor, Service Health And Azure Monitor — Microsoft Azure Fundamentals (AZ-900) Exam Prep
- The Shared Responsibility Model — Cloud Infrastructure & Hyperscaler Architecture
- Regions, Availability Zones and Reliability — Cloud Infrastructure & Hyperscaler Architecture
- Network Address Translation — Cloud Infrastructure & Hyperscaler Architecture
- Elastic Compute Cloud (EC2) — Cloud Infrastructure & Hyperscaler Architecture
- Serverless Compute (Lambda) — Cloud Infrastructure & Hyperscaler Architecture
- Auto Scaling Groups — Cloud Infrastructure & Hyperscaler Architecture
- Object, Block, and File Storage — Cloud Infrastructure & Hyperscaler Architecture
- How Bills Actually Get Large — Cloud Infrastructure & Hyperscaler Architecture
- The Four Keys History And Retiring MTTR — DevOps & Site Reliability Engineering
- Percentiles Rather Than Averages — DevOps & Site Reliability Engineering
- Service Level Objectives — DevOps & Site Reliability Engineering
- Error Budgets — DevOps & Site Reliability Engineering
- Requirements: The Constraints That Shape The System — Scalable System Design & Distributed Architecture
- Caching Strategies And Topology — Scalable System Design & Distributed Architecture
- Observability As A Design Input — Scalable System Design & Distributed Architecture
References
- NIST glossary: reliability
- Google SRE book: Embracing Risk
- AWS Well-Architected Reliability pillar
- Google Cloud Architecture Framework: Reliability