Topic lessonTopic: availability and performance
Availability vs performance: understanding redundancy and scaling
“Keep it usable” and “make it fast” need different checks. Availability concerns correct use when needed; performance concerns speed and processing volume under defined demand. Use the same report task and a fictional AWS Availability Zone (AZ) failure to distinguish passing one criterion from passing both.
Separate normal-performance criteria from continuity during a stated failure, judge fixed results as pass, fail or not checked, and identify further checks for redundancy and capacity changes.
Understand Regions, AZs and shared versus separate failure boundaries. No EC2 or database configuration knowledge is needed. Timing runs from the client sending a request to receiving the correct response.
Separate staying usable from processing work fast enough
Availability concerns whether a workload can perform its agreed function correctly when needed. Performance concerns response speed and the amount of work processed under defined demand and operating conditions. Response time is the time from sending a request to receiving its response; throughput is work completed per unit of time. Instance counts and CPU utilization are not substitutes for the result a user needs.
To express availability as a percentage, first define an observation period, such as a month, and what counts as available; then use a measure such as available time within that period.
- Read the required report → Usable during a failure?Define the continuity conditions
- Read the required report → Fast enough for the demand?Define speed and work-volume conditions
- Usable during a failure? → Check matching evidenceUse results for the stated failure
- Fast enough for the demand? → Check matching evidenceUse results for the stated demand
- Read the required report
- Define the correct result first.
- Usable during a failure?
- Specify the failure, required result and acceptable wait.
- Fast enough for the demand?
- Specify concurrent requests and response criteria.
- Check matching evidence
- Placement and instance counts do not prove success.
The lines connect requirements to checks. They are not network paths, request order or failure propagation. Separating the questions makes missing evidence easier to identify.
Fixed example: two checks for the same report task
An employee needs the required internal report. Keep input size, required data and the client-side timing boundary consistent. The following two trials are fictional, not AWS measurements. One checks normal-operation performance; the other checks continued use during a specific failure.
| Question | Trial conditions | Pass criterion for this example |
|---|---|---|
| Normal-operation performance | No failure. Send 3 requests simultaneously. | All 3 return the correct report within 300 ms each. |
| Continuity during an AZ failure | AZ-A is unavailable. Send 3 requests simultaneously. | All 3 return the correct report within 2 seconds (2,000 ms) each. |
| Case | 3 normal-operation response times | 3 AZ-A-failure response times | Normal performance | Failure continuity |
|---|---|---|---|---|
| A | 150 / 220 / 300 ms; all correct | No correct response for any request by 2 seconds | Pass | Fail |
| B | 550 / 650 / 800 ms; all correct | 1,000 / 1,500 / 2,000 ms; all correct | Fail | Pass |
| C | 120 / 200 / 280 ms; all correct | 900 / 1,200 / 1,800 ms; all correct | Pass | Pass |
| D | 120 / 200 / 280 ms; all correct | No result checked | Pass | Not checked |
A is fast in normal operation but does not continue serving the required result under the stated failure. B meets the 2-second failure condition while missing the normal-operation 300-ms condition. C meets both conditions in this example. For D, do not invent a failure result from normal-operation speed.
These are given observations, not response times predicted from a topology. No row is calculated from placement alone. A fast HTTP 200 with the wrong report is not a correct result. C exceeds 300 ms during the failure, but the current performance criterion applies only to normal operation. If users also require 300 ms during the failure, add that condition and check it separately.
Choose redundancy and scaling from the requirements
Redundancy provides alternative components or paths so that required work can continue when an element becomes unavailable. Scaling changes capacity to match demand. You can change the size of an element or change the number of elements. Consider whether required work continues after capacity decreases as well as after it increases.
| Option | Potential use | What it does not establish alone |
|---|---|---|
| Provide processing destinations in another AZ | Prepare for one AZ becoming unavailable | Request failover, required data, remaining capacity and shared dependencies |
| Change the number of equivalent processing elements | Match capacity to changing concurrent demand | Whether a common failure stops all elements, and whether app/storage design can use the capacity |
| Change one element’s capacity | A candidate when CPU or memory is insufficient | Whether that resource is the actual bottleneck; change downtime, limits and costs |
| Combine request distribution with required processing destinations | Use multiple destinations | Health criteria, app state, data and the actual user result |
In AWS, Auto Scaling can maintain or change capacity, while ELB supplies request distribution as part of a design. Adding these components does not demonstrate that users’ requirements are met. State the required outcome before moving into service configuration.
Practice matching results to requirements
Choose an option to see the result and explanation.
Choose an option to see the result and explanation.
Move from requirements to architecture checks
- Write what the user must complete for the result to count as correct.
- Specify normal demand, input and response-time conditions.
- Specify the failure and the required outcome and wait during it.
- Connect placement, failover, data, remaining capacity and shared dependencies to the requirements.
- Separate pass, fail and not checked; retain the periods and demand conditions not evaluated.
Choose a related lesson for your next question
- Review AZ placement and remaining failure boundaries:Review Regions and AZs →
- Learn capacity maintenance and scaling after checking the EC2 prerequisites:Read about EC2 Auto Scaling →
- Learn request distribution after checking HTTP and networking prerequisites:Read about ELB components →
- For readers with database/RDS knowledge, compare availability and read distribution:Compare RDS deployments →
Check, then explain in your own words
- Separate continuity from speed requirements for the same task.
- Match normal and failure results to their own deadlines.
- Identify remaining checks for redundancy, capacity changes and distribution.
Check your understanding: Does a fast normal response establish that the app remains usable during an AZ failure?
No. Check the required result and acceptable wait under that failure condition separately.
The condition used to assess speed differs from the failure condition that must be handled. Check failover, data, remaining capacity and shared dependencies as well as placement and counts.
Sources and conditions checked
Primary references are collected here with their scope, conditions and corresponding sections. Independent expert review and live-environment validation have not been performed.
Scope and conditionsAvailability concerns successful agreed functionality when needed, with explicit timing and measurement scope. This lesson uses stipulated trials, not monthly uptime, SLA guarantees or independent-component probability calculations.
Used in this lessonSeparate staying usable from processing work fast enough
Scope and conditionsState latency, throughput, traffic patterns and other workload conditions before evaluating performance. This network-focused reference does not prescribe the lesson's fictional three-request trial or 300-ms target, and does not establish actual application performance.
Used in this lessonSeparate staying usable from processing work fast enough
Scope and conditionsRedundant smaller resources and horizontal scaling can support availability if shared failure points are considered. Recovery and capacity must be tested against business outcomes. Do not assume redundancy and scaling affect only one requirement each.
Used in this lessonChoose redundancy and scaling from the requirements
Scope and conditionsCapacity can change vertically by size or horizontally by count to match demand. The chosen approach, scaling metric and behavior after scale-in need workload-specific validation; increasing capacity is not a measured performance or cost guarantee.
Used in this lessonChoose redundancy and scaling from the requirements
- What is Amazon EC2 Auto Scaling?Checked:
Scope and conditionsGroup management, maintaining desired capacity, configured demand scaling and separate request distribution. Not automatic application availability.
Used in this lessonChoose redundancy and scaling from the requirements