Cloud concept · Updated

Composite Availability - Composite availability is the end-to-end availability of a system determined by its required dependencies, redundant components, and failure relationships.

In short

A cloud application can be unavailable even when most of its components are healthy, because successful requests may require several services to work together. Composite availability helps engineers evaluate architecture choices, estimate whether business availability targets are achievable, and distinguish application commitments from individual provider SLAs.

Cloud Concepts Hub →

6 key aspects of Composite Availability

Composite availability combines dependency structure, redundancy, failure correlation, and measured recovery behavior to evaluate end-to-end business availability.

01
User-centered success criteria

Define availability for a specific business operation, including correctness and acceptable latency. A healthy infrastructure dashboard does not prove that users can complete that operation.

02
Required dependency multiplication

For independent components that must all work, multiply their availability fractions. Adding mandatory synchronous dependencies generally reduces the modeled end-to-end availability.

03
Redundant-path availability

When any alternative can independently satisfy the workload, calculate one minus the probability that all alternatives are unavailable. Include routing, capacity, and failover limitations before treating alternatives as interchangeable.

04
Common-cause failure analysis

Identify shared infrastructure, configuration, credentials, and deployment risks. Replicas do not provide the theoretical benefit of independent redundancy when a single event can disable them together.

05
SLA and objective alignment

Compare the application's modeled and observed availability with its business objective. Review provider SLA terms separately because component commitments do not automatically become an end-to-end application commitment.

06
Operational validation

Measure complete transactions and test failure recovery under realistic load. Account for detection delays, connection recovery, insufficient surviving capacity, and unsuccessful retries.

Cloud services for Composite Availability

Elastic Load Balancing and Amazon EC2 Auto Scaling support a redundant application tier by routing requests across healthy capacity and replacing failed instances. Amazon RDS Multi-AZ configurations address database failure scenarios, while Amazon Route 53 can direct clients toward alternate endpoints when the architecture supports them. Amazon CloudWatch provides measurements and synthetic checks to validate whether the complete request path remains usable. These services must be evaluated as a dependency graph rather than as independent availability guarantees: shared dependencies, detection delays, database recovery, DNS caching, and insufficient failover capacity can all reduce the availability experienced by users.

Amazon EC2 Auto ScalingAmazon EC2 Auto Scaling

Amazon EC2 Auto Scaling can maintain application capacity across multiple Availability Zones and replace unhealthy instances. Replacement takes time, so sufficient surviving capacity is necessary to avoid treating eventual recovery as uninterrupted availability.

Amazon RDSAmazon RDS

Amazon RDS Multi-AZ configurations provide database redundancy and managed failover capabilities. Database failover and application reconnection can still interrupt requests, so the database tier's contribution must reflect the selected configuration and observed recovery behavior.

Amazon Route 53Amazon Route 53

Amazon Route 53 supports health-check-based DNS failover between endpoints. DNS caching, health detection, and the readiness of the alternate endpoint affect how quickly users regain service.

Amazon CloudWatchAmazon CloudWatch

Amazon CloudWatch collects metrics, logs, and alarms that help identify failures across required dependencies. CloudWatch Synthetics can exercise user-facing workflows to measure availability beyond individual resource health.

Composite Availability exam questions

Real practice exam questions on Composite Availability, with the correct answer and its explanation. Answer them with every option in the exam simulator.

DOP-C02

A company operates an API through two Amazon EC2 application pools in different Availability Zones. Either pool can handle the full workload. Both pools use the same Amazon RDS database deployment, and every successful request requires a database operation. Routing automatically selects an available pool.

For an architecture review, a DevOps engineer models each application pool as 99.9% available and the shared database deployment as 99.95% available. Assume that availability events for the two pools and the database deployment are mutually independent. Ignore routing failures, failover delays, and all other dependencies. These percentages are planning assumptions, not AWS contractual commitments.

The company is considering a 99.99% customer-facing availability commitment. Which assessment correctly evaluates whether the modeled architecture supports this commitment?

Show answerCORRECT ANSWER

The estimated availability is approximately 99.9499%, which does not support the proposed commitment. Combine the application pools as alternatives, and then multiply that result by the shared database's availability.

The application tier is available when either pool is available: 1 − (1 − 0.999)² = 0.999999. A successful request also requires the shared database, so total availability is 0.999999 × 0.9995 = 0.9994990005, or approximately 99.9499%. Compute redundancy does not remove the required database dependency, and the modeled result is below 99.99%.

Practice Composite Availability in a full exam

Questions on Composite Availability in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Composite Availability

3 min read

Composite availability describes whether an entire application or business operation is usable, rather than whether an individual component is running. Begin by defining success from the user's perspective: for example, a checkout request must complete correctly within two seconds. Then identify the dependencies required for that operation, including traffic routing, application compute, authentication, databases, and external payment systems. Different operations can have different availability because they follow different dependency paths.

When every component in a path must work, those components form a series dependency. Under an assumption of independent availability events, the composite availability is the product of their individual availabilities: A = A1 × A2 × ... × An. For example, three required tiers, each with an assumed availability of 99.9%, produce 0.999³, or approximately 99.7003%. Over a 30-day month, that corresponds to approximately 129.5 minutes of unavailability, compared with 43.2 minutes for a 99.9% target. These are modeling examples, not published service commitments.

Redundancy changes the calculation when any one of several alternatives can satisfy the operation. For independent alternatives, availability is A = 1 − ((1 − A1) × (1 − A2) × ... × (1 − An)). Two independent alternatives, each available 99.9% of the time, yield a theoretical 99.9999%. This assumes either alternative can serve the workload successfully and that detection, routing, failover, and state requirements do not introduce additional failures. A redundant application tier may improve substantially while the overall application remains constrained by a required database or identity provider.

Real cloud failures are not always independent. Instances in the same Availability Zone can share infrastructure risks, while instances in different zones can still share a faulty deployment, exhausted quota, credential problem, or regional dependency. The probability formulas are useful architectural models, not guarantees. Explicitly model shared dependencies and common-cause failures rather than applying the parallel formula to replicas that fail together.

Apply the concept by distributing application capacity across failure domains, using health-aware routing, and ensuring surviving capacity can handle expected traffic. For a database-dependent application, evaluate database failover time, connection recovery, and transaction retry behavior. A standby that requires promotion is not equivalent to an immediately usable independent replica. Test failure scenarios to measure the user-visible interruption rather than assuming that redundancy eliminates downtime.

Reducing mandatory dependencies can also improve availability. An order service might commit an order and queue a notification instead of requiring the email system to respond before checkout succeeds. This improves the checkout dependency path, but it introduces eventual processing and requires durable queuing, idempotency, and backlog monitoring. Graceful degradation is valid only when the reduced behavior still meets the defined business requirement.

For SLA questions, distinguish a contractual service-level agreement from an internal service-level objective and a measured service-level indicator. A provider SLA defines its own scope, measurement method, exclusions, and remedies; multiplying advertised SLA percentages does not create a contractual application guarantee. Assess the assumptions stated in an exam scenario, calculate series or parallel availability where appropriate, and compare the result with the business target. In production, validate the model with end-to-end measurements, incident history, and failover tests, balancing greater redundancy against cost and operational complexity.

Learn Composite Availability in lessons

1 short lesson on Composite Availability in 1 certification course.

Open the lessons