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.
In more detail
It is often measured as successful requests divided by valid requests over a time window, which is better than asking whether a process is up, because a running process can still fail every request. Availability is lost when a service goes down, a disk fails or ransomware locks files, even if nothing was stolen or changed. In security it is one of the three goals of the CIA triad, alongside confidentiality and integrity. It is different from durability, which asks whether stored data survives.
Examples
The file server is encrypted on the morning payroll is due, so nobody gets paid.99 percent allows over 7 hours a month; 99.9 allows about 43 minutes; 99.99 about 4 minutes.Related terms
- durability — The likelihood that stored data survives hardware failures without being lost, usually stated as a percentage per year.
- high availability — Designing a system so it keeps working when one part fails, usually by running redundant copies with no single point of failure.
- 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.
- CIA triad — The three core goals of security: confidentiality (only the right people see data), integrity (data is not wrongly changed) and availability (systems work when needed).
- backup — An extra copy of data kept separately so it can be restored if the original is lost, damaged, deleted or encrypted by an attacker.
- ransomware — Malware that encrypts or steals an organisation's data and demands payment to restore it or keep it private.
- reliability — The ability of a system to keep doing its job correctly, including recovering from failures, for as long as it is needed.
- service level indicator — A measurement of how well a service is doing for users, usually good events divided by eligible events.
- rolling update — Replacing instances of an application with the new version a few at a time while the rest keep serving.
- health endpoint — A web address, often /health, that a service answers quickly to show it is up.
- downtime — Time during which a system is unavailable to its users.
- uptime — Time during which a system is running and serving users, usually quoted as a percentage.
- hard dependency — A dependency whose failure makes your own request fail, so its availability multiplies into yours.
- CAP theorem — The result that during a network partition a replicated system must choose between consistent answers and answering every request.
- 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.
Taught in
- The Night Larder Could Not Buy Servers Fast Enough — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Ninety Minutes, Sixty Five Questions — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Six Advantages, In AWS's Own Words — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Ten Findings, Six Pillars — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Cloud Concepts Sprint: Twelve Cards — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- The Root Key In The Backup Script — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- The Morning An Availability Zone Went Dark — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Reading A 130-Minute Exam — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- The Network As A Control: CIDR, Routes, ACLs And Security Groups — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Private Paths: VPC Endpoints And PrivateLink — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Load Balancers And Auto Scaling: Capacity That Arrives On Time — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Databases That Survive: Standbys, Replicas And Global Tables — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Storage Performance: IOPS, Throughput And The Right Volume — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Compute Performance: Families, Placement And Lambda Memory — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- The Performance Clinic: Five Slow Systems, Five Fixes — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Storage Cost: Classes, Lifecycle Rules And The Retrieval Trap — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Compute Cost: Commit, Interrupt Or Pay As You Go — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Database Cost: Serverless, Capacity Modes And Reservations — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Network Cost: NAT Gateways, Zones And Data Out — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Long-Stem Clinic: The Phrase That Decides — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- The Full Mock And Your Review Plan — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- The Shared Responsibility Model — Cloud Infrastructure & Hyperscaler Architecture
- Regions, Availability Zones and Reliability — Cloud Infrastructure & Hyperscaler Architecture
- Virtual Private Clouds — Cloud Infrastructure & Hyperscaler Architecture
- Network Address Translation — Cloud Infrastructure & Hyperscaler Architecture
- Containers on AWS (ECS and EKS) — Cloud Infrastructure & Hyperscaler Architecture
- Comparing Compute Options — Cloud Infrastructure & Hyperscaler Architecture
- Auto Scaling Groups — Cloud Infrastructure & Hyperscaler Architecture
- Object, Block, and File Storage — Cloud Infrastructure & Hyperscaler Architecture
- Elastic Block Store (EBS) — Cloud Infrastructure & Hyperscaler Architecture
- Elastic File System (EFS) — Cloud Infrastructure & Hyperscaler Architecture
- Managed Relational Databases (RDS) — Cloud Infrastructure & Hyperscaler Architecture
- When to Pick Which Database — Cloud Infrastructure & Hyperscaler Architecture
- Observability with CloudWatch — Cloud Infrastructure & Hyperscaler Architecture
- CIA Triad, Non-Repudiation & Parkerian Hexad — Cybersecurity Fundamentals, GRC & Cryptography
- Regulatory Compliance: SOC 2, HIPAA, GDPR & PCI-DSS — Cybersecurity Fundamentals, GRC & Cryptography
- Vendor & Third-Party Risk Management Programs — Cybersecurity Fundamentals, GRC & Cryptography
- Data Classification Schemes & Sensitivity Labeling — Cybersecurity Fundamentals, GRC & Cryptography
- Business Impact Analysis, RTO & RPO Modeling — Cybersecurity Fundamentals, GRC & Cryptography
- Security Capstone Review & Certification — Cybersecurity Fundamentals, GRC & Cryptography
- The Four Keys History And Retiring MTTR — DevOps & Site Reliability Engineering
- Deployment Strategies: Rolling Updates — DevOps & Site Reliability Engineering
- Service Level Indicators — DevOps & Site Reliability Engineering
- Service Level Indicators — Full-Stack Observability: Metrics, Tracing & Logging
- Ninety Nine Percent Of What? SLIs, SLOs And SLAs — Prometheus Certified Associate (PCA) Exam Prep
- Where Did Two Hours Go? Prometheus Architecture — Prometheus Certified Associate (PCA) Exam Prep
- Fifteen Requests Nobody Saw: Aggregating Over Time — Prometheus Certified Associate (PCA) Exam Prep
- PromQL Sprint: Ten Queries At Minute Twenty Two — Prometheus Certified Associate (PCA) Exam Prep
- Seventy Seven Percent, Book Now? The Full Mock — Prometheus Certified Associate (PCA) Exam Prep
- Requirements: The Constraints That Shape The System — Scalable System Design & Distributed Architecture
- Back Of The Envelope Estimation: Traffic And Throughput — Scalable System Design & Distributed Architecture
- Back Of The Envelope Estimation: Storage And Bandwidth — Scalable System Design & Distributed Architecture
- Replication, Failover And Leader Election — Scalable System Design & Distributed Architecture
- Consistency, And The Truth About CAP — Scalable System Design & Distributed Architecture
- Monolith Versus Services: The Honest Trade Offs — Scalable System Design & Distributed Architecture
- Observability As A Design Input — Scalable System Design & Distributed Architecture
- Capacity Planning As A Design Input — Scalable System Design & Distributed Architecture
- Worked Design Three: A Metrics Ingestion Pipeline — Scalable System Design & Distributed Architecture
- Worked Design Three: Scaling The Metrics Pipeline — Scalable System Design & Distributed Architecture
References
- AWS Well-Architected Reliability pillar: availability
- NIST glossary: availability
- Google SRE book: Embracing Risk
- Google SRE book: service level objectives
- Google SRE book: Availability Table
- AWS whitepaper: Availability and Beyond