What it means
Availability means that authorized users can obtain the service or information they need within acceptable conditions. The requirement is about useful service, not simply whether a computer answers a network check. A website can respond while its booking database is unavailable, leaving the actual business task impossible.
Start by defining what must work, for whom, and when. Then examine dependencies, capacity, failure handling, recovery, and operational support. Redundant components can help, but shared dependencies can still fail together. Planned maintenance and safe fallback procedures are part of availability engineering as much as protection against deliberate disruption.
AN ILLUSTRATIVE SCENARIO
A transport dispatch service
A transport operator depends on a dispatch service during its morning departures. A routine infrastructure dashboard shows the web server running, but drivers cannot retrieve assignments because the identity service is unavailable. The operations team uses a documented temporary dispatch process while administrators restore access. Afterwards, the team adds an end-to-end check for the driver workflow and exercises the fallback. The incident shows why service availability must include authentication and other dependencies, rather than only the main application host.
Put it to work
- Define the critical user task and acceptable disruption with its owner, including important times, dependencies, and any safety-related constraints.
- Choose measures such as capacity planning, redundancy, monitoring, tested recovery, and practical fallback procedures based on that requirement.
- Test realistic dependency failures in a controlled setting and measure whether the user task and recovery process meet the agreed expectations.
How to check your work
Run a representative end-to-end task and a controlled recovery exercise. Record the observed service interruption and restoration result, including any dependency or manual step that limits the claimed availability.
Connect the ideas
- CIA triad
A shorthand for naming whether a loss is disclosure, unauthorized change, or downtime.
- Backup
A copy of data kept so integrity and availability can be restored after loss, preferably beyond the production identity’s reach.
- Ransomware
Malware or an operator model that denies availability of data, often by encryption, sometimes with theft for extra pressure.
- Defense in depth
Layering independent controls so that one failure does not become a complete compromise.