Availability
Availability is counted in nines, and each nine is ten times harder
Availability is the share of time a system works. 99.9% allows nearly nine hours of downtime a year; 99.99% allows 53 minutes.
How reliable is reliable? The industry counts it in nines. Ninety-nine percent sounds excellent. It allows more than three and a half days of downtime every year. Add a nine. Ninety-nine point nine percent: just under nine hours. Four nines: fifty-three minutes in a whole year. This is what most cloud services promise when you spread across zones. Five nines: five minutes. Each extra nine cuts the downtime by ten, and costs far more to achieve than the one before. So the real question is how much downtime each system can afford.
Availability · Going deeper
Service level agreements, and how availability combines
An SLA is a promised availability. Parts in series multiply it down; redundant parts multiply it up.
High availability
No single point of failure: two of everything, kept apart
A single point of failure is any part whose loss stops the system. Remove them with redundancy across zones.
Reaching those nines is a matter of design. Here is the simplest system: one server and one database, in one zone. It has three single points of failure. If the server dies, the site is down. If the database dies, the same. If the zone has a power failure, everything goes at once. Now double it. Two servers in two zones behind a load balancer, and a database with a standby in the second zone. Take away any one part, even a whole zone, and the other half keeps serving. Nothing here is new. You have met every piece in the last seven lessons.
High availability · Going deeper · 1 of 2
High availability, fault tolerance and disaster recovery
High availability recovers quickly, fault tolerance does not stop at all, and disaster recovery restores service after losing a region.
High availability · Going deeper · 2 of 2
The words the exams use
Fundamentals exams test a handful of terms for the benefits of cloud. Each has a precise meaning.
Fundamentals exams test a handful of terms for the benefits of cloud. Each has a precise meaning. High availability the system keeps working despite failures, measured as a percentage of time. Reliability it recovers from failures and keeps doing what it should. The cloud helps by letting you spread across zones and regions. Scalability it can grow to meet demand. Vertical: a bigger machine. Horizontal: more machines. Elasticity it grows and shrinks automatically as demand changes, so you do not pay for idle capacity. Agility resources can be created and changed in minutes. Predictability performance and cost can be forecast, using autoscaling, load balancing and cost tools. Governance and manageability rules are applied automatically (policies, templates) and everything can be managed through a portal, a command line or code. Scalability is the ability to grow; elasticity is doing it automatically in both directions. An exam answer that mentions “automatically” or “shrinks” is describing elasticity.
- High availability the system keeps working despite failures, measured as a percentage of time.
- Reliability it recovers from failures and keeps doing what it should. The cloud helps by letting you spread across zones and regions.
- Scalability it can grow to meet demand. Vertical: a bigger machine. Horizontal: more machines.
- Elasticity it grows and shrinks automatically as demand changes, so you do not pay for idle capacity.
- Agility resources can be created and changed in minutes.
- Predictability performance and cost can be forecast, using autoscaling, load balancing and cost tools.
- Governance and manageability rules are applied automatically (policies, templates) and everything can be managed through a portal, a command line or code.
Disaster recovery
Two numbers define a recovery plan: data lost, and time down
RPO is how much data you can afford to lose; RTO is how long you can afford to be down.
Zones protect against ordinary failures. A disaster is the day a whole region is lost, or the data is destroyed. Planning for it starts with two numbers. Suppose the last backup was taken at two in the morning. At eleven, disaster. Everything written in those nine hours is gone. The amount of data you can bear to lose is the recovery point objective. It tells you how often to back up or copy your data. Service returns at three in the afternoon, four hours later. The time you can bear to be down is the recovery time objective. It tells you how much must be ready and waiting.
Disaster recovery · Going deeper
Four recovery strategies, from cheap and slow to instant
Backup and restore, pilot light, warm standby and active in two regions trade cost against recovery time.
Monitoring
You cannot fix what you cannot see: metrics, logs and traces
Metrics show that something is wrong, logs show what, and traces show where.
A system built to survive failures still has to be watched, or small problems grow unseen. Three kinds of signal do the watching. Metrics are numbers measured every minute: how busy the processors are, how many requests arrive. A metric climbing past its limit says that something is wrong. Logs are the lines software writes as things happen. Here, payments are timing out. Logs say what went wrong. A trace follows one request through every service it touches, timing each step. This one shows the database taking nearly three seconds. Traces say where. Together they turn “the site is slow” into a specific fault.
Monitoring · Going deeper · 1 of 2
Alarms: a limit, a duration and an action
An alarm fires when a metric stays past a limit, then notifies people or triggers an automatic fix such as scaling out.
Monitoring · Going deeper · 2 of 2
The operations services, by the question each answers
CloudWatch and Azure Monitor watch behaviour; CloudTrail and the Activity Log record actions; health dashboards report the provider’s own incidents.
Infrastructure as code
Describe the system in a file, and it can be rebuilt identically
Infrastructure as code defines networks, servers and databases in a template that tools turn into real resources.
One practice ties reliability together. Instead of building the system by clicking through a console, you describe it in a text file: the network, the zones, four servers behind a balancer, a database with a standby, the alarms. A tool reads the file and creates exactly that. Run it once and you have a test environment. Run it again for production, and the two are identical. And if a region is ever lost, run it a third time somewhere else. The system can be rebuilt in minutes because its design is written down, not remembered.
Infrastructure as code · Going deeper
Four ways to operate a cloud
Everything in a cloud is done through its API. There are four ways to call it, suited to different work.
Everything in a cloud is done through its API. There are four ways to call it, suited to different work. The web console (portal) point and click in a browser. Best for learning, exploring and one-off checks. The command line typed commands that can be saved in scripts: the AWS CLI, Azure CLI and Azure PowerShell, the gcloud CLI. Each provider also offers a browser-based shell with these tools installed: CloudShell, Azure Cloud Shell, Cloud Shell. Software development kits (SDKs) libraries for calling the cloud from your own programs. Infrastructure as code templates that declare the end state: CloudFormation, ARM templates and Bicep, Terraform. Scripts say how to build something, step by step. Templates say what should exist, and the tool works out the steps, including what to change when the template is edited. That is why templates are preferred for anything that lasts. Managing beyond one cloud. Azure Arc extends Azure’s management tools to servers in your own data centre and in other clouds. AWS Systems Manager and Google’s fleet tools do similar work for mixed estates.
- The web console (portal) point and click in a browser. Best for learning, exploring and one-off checks.
- The command line typed commands that can be saved in scripts: the AWS CLI, Azure CLI and Azure PowerShell, the gcloud CLI. Each provider also offers a browser-based shell with these tools installed: CloudShell, Azure Cloud Shell, Cloud Shell.
- Software development kits (SDKs) libraries for calling the cloud from your own programs.
- Infrastructure as code templates that declare the end state: CloudFormation, ARM templates and Bicep, Terraform.
Managing beyond one cloud
Azure Arc extends Azure’s management tools to servers in your own data centre and in other clouds. AWS Systems Manager and Google’s fleet tools do similar work for mixed estates.
Support plans
Support is a paid plan: you buy how fast an engineer answers
A support plan sets who you can contact and how fast they respond, from 12 hours down to 15 minutes.
When something breaks that you cannot fix, you need the provider’s engineers, and that is a service you pay for. Take AWS. Every account has Basic support: help with bills and the account, but no engineers. Developer adds technical help by email, with an answer within twelve hours if a system is impaired. Business is the first plan meant for production: any time, any day, and a response within an hour when production is down. Enterprise On-Ramp halves that to thirty minutes. And Enterprise answers in fifteen, and gives you a named manager who knows your systems.
Well-architected design
Six questions judge any design, and you can now answer them
The Well-Architected Framework reviews a system against six pillars: operations, security, reliability, performance, cost and sustainability.
To finish, here is how the providers themselves judge a design. Six questions. Can you run it and change it safely? That was this lesson. Who can reach what? Shared responsibility, networking, and identity. Does it survive a failure? Zones, managed databases, and today. Is each part the right kind and size? Compute, storage, and data services. Do you pay only for what you need? The first lesson and the ninth. And does it use as little energy as it can? These pull against each other, and choosing the balance is the architect’s job. You now know what each choice involves.
Well-architected design · Going deeper
The frameworks on each provider, and what to do next
All three providers publish a free framework and a review tool. They are the best next reading after this course.
All three providers publish a free framework and a review tool. They are the best next reading after this course. The frameworks. AWS Well-Architected Framework six pillars, with the Well-Architected Tool in the console to review a workload against them. Azure Well-Architected Framework five pillars: reliability, security, cost optimisation, operational excellence and performance efficiency. The Cloud Adoption Framework covers the move to the cloud itself. Google Cloud Architecture Framework the same themes: operational excellence, security, reliability, cost and performance optimisation, with sustainability. Where this course leads. A fundamentals exam AWS Certified Cloud Practitioner, Microsoft Azure Fundamentals (AZ-900) or Google Cloud Digital Leader. Each has its own course here, built on these ten lessons. An associate exam Solutions Architect Associate or Azure Administrator (AZ-104), once the fundamentals are solid. Practice open a free-tier account, set a budget alert first, and build the two-zone application from this lesson.
The frameworks
- AWS Well-Architected Framework six pillars, with the Well-Architected Tool in the console to review a workload against them.
- Azure Well-Architected Framework five pillars: reliability, security, cost optimisation, operational excellence and performance efficiency. The Cloud Adoption Framework covers the move to the cloud itself.
- Google Cloud Architecture Framework the same themes: operational excellence, security, reliability, cost and performance optimisation, with sustainability.
Where this course leads
- A fundamentals exam AWS Certified Cloud Practitioner, Microsoft Azure Fundamentals (AZ-900) or Google Cloud Digital Leader. Each has its own course here, built on these ten lessons.
- An associate exam Solutions Architect Associate or Azure Administrator (AZ-104), once the fundamentals are solid.
- Practice open a free-tier account, set a budget alert first, and build the two-zone application from this lesson.
Lesson complete
You finished “Availability, monitoring and support”
Nicely done.