Bird
Raised Fist0
AWScloud~5 mins

High availability design patterns in AWS - Time & Space Complexity

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
Time Complexity: High availability design patterns
O(n)
Understanding Time Complexity

We want to understand how the effort to keep a system always running grows as we add more parts to it.

How does adding more servers or resources affect the work needed to maintain high availability?

Scenario Under Consideration

Analyze the time complexity of deploying a multi-AZ load balanced web service.


aws ec2 run-instances --count n --image-id ami-12345678 --subnet-id subnet-abcde
aws elbv2 create-load-balancer --name my-lb --subnets subnet-abcde subnet-fghij
aws elbv2 register-targets --target-group-arn arn:tg --targets Id=i-12345 Id=i-67890
aws elbv2 create-listener --load-balancer-arn arn:lb --protocol HTTP --port 80 --default-actions Type=forward,TargetGroupArn=arn:tg

This sequence launches n instances across availability zones, sets up a load balancer, and connects instances to it.

Identify Repeating Operations

Look at what repeats as we add more instances.

  • Primary operation: Launching EC2 instances (run-instances) and registering them to the load balancer.
  • How many times: The launch and registration happen once per instance, so n times.
How Execution Grows With Input

As you add more instances, you launch and register more servers one by one.

Input Size (n)Approx. Api Calls/Operations
10About 10 launches + 10 registrations = 20 calls
100About 100 launches + 100 registrations = 200 calls
1000About 1000 launches + 1000 registrations = 2000 calls

Pattern observation: The number of calls grows directly with the number of instances added.

Final Time Complexity

Time Complexity: O(n)

This means the work to deploy and connect instances grows in a straight line as you add more servers.

Common Mistake

[X] Wrong: "Adding more servers does not increase deployment time because everything happens at once."

[OK] Correct: Each server requires its own setup and registration, so the total work grows with the number of servers.

Interview Connect

Understanding how adding resources affects deployment effort helps you design systems that stay reliable without surprises.

Self-Check

"What if we used an auto-scaling group to manage instances instead of launching each manually? How would the time complexity change?"

Practice

(1/5)
1. What is the main goal of a high availability design pattern in AWS?
easy
A. To reduce the cost of cloud resources
B. To keep the application running even if some parts fail
C. To increase the speed of the application only
D. To limit the number of users accessing the app

Solution

  1. Step 1: Understand high availability concept

    High availability means designing systems to stay online and functional despite failures.

  2. Step 2: Match goal with options

    Only To keep the application running even if some parts fail describes keeping the app running during failures, which is the goal.

  3. Final Answer:

    To keep the application running even if some parts fail -> Option B

  4. Quick Check:

    High availability = keep running despite failures [OK]
Hint: High availability means no downtime during failures [OK]
Common Mistakes:
  • Confusing cost reduction with availability
  • Thinking speed alone defines high availability
  • Assuming limiting users improves availability
2. Which AWS service is commonly used to distribute incoming traffic across multiple instances for high availability?
easy
A. Amazon S3
B. AWS Lambda
C. Amazon RDS
D. Elastic Load Balancer (ELB)

Solution

  1. Step 1: Identify service for traffic distribution

    Elastic Load Balancer (ELB) distributes traffic to multiple instances to avoid single points of failure.

  2. Step 2: Eliminate other options

    Amazon S3 stores files, RDS is a database, Lambda runs code; none distribute traffic.

  3. Final Answer:

    Elastic Load Balancer (ELB) -> Option D

  4. Quick Check:

    Traffic distribution = ELB [OK]
Hint: Load balancers spread traffic to keep apps available [OK]
Common Mistakes:
  • Choosing storage or compute services instead of load balancer
  • Confusing Lambda with traffic distribution
  • Selecting database services for traffic handling
3. Consider this AWS setup: An application runs in two Availability Zones (AZs) behind an Elastic Load Balancer. If one AZ fails, what happens to the app availability?
medium
A. The app slows down but stays available in the failed AZ
B. The app becomes completely unavailable
C. The app continues running using the healthy AZ
D. The app automatically scales down to zero instances

Solution

  1. Step 1: Understand multi-AZ deployment

    Running in multiple AZs means if one AZ fails, others can serve traffic.

  2. Step 2: Analyze ELB behavior

    ELB routes traffic only to healthy instances, so app stays available in the healthy AZ.

  3. Final Answer:

    The app continues running using the healthy AZ -> Option C

  4. Quick Check:

    Multi-AZ + ELB = app stays available [OK]
Hint: Multi-AZ with ELB keeps app running if one AZ fails [OK]
Common Mistakes:
  • Assuming total outage if one AZ fails
  • Thinking app slows but serves from failed AZ
  • Believing app scales down automatically on failure
4. You configured an Auto Scaling group with minimum 2 instances across two AZs, but during a failure, only one instance is running. What is the likely issue?
medium
A. Auto Scaling group is not set to replace unhealthy instances
B. Load balancer is misconfigured to route traffic
C. Instances are launched in the same AZ only
D. Security groups block instance communication

Solution

  1. Step 1: Check Auto Scaling group settings

    Auto Scaling must replace unhealthy instances to maintain minimum capacity.

  2. Step 2: Understand failure impact

    If replacement is disabled, failed instance won't be replaced, causing fewer running instances.

  3. Final Answer:

    Auto Scaling group is not set to replace unhealthy instances -> Option A

  4. Quick Check:

    Auto Scaling replaces unhealthy = maintain capacity [OK]
Hint: Auto Scaling must replace failed instances to keep count [OK]
Common Mistakes:
  • Blaming load balancer for instance count
  • Assuming instances launched only in one AZ
  • Thinking security groups affect instance count
5. You want to design a highly available web app on AWS that stays online even if an entire region fails. Which combination should you use?
hard
A. Deploy instances in multiple regions with Route 53 latency-based routing and health checks
B. Deploy instances in multiple AZs within one region and use an Elastic Load Balancer
C. Use a single instance in one AZ with Auto Scaling enabled
D. Deploy instances in one AZ and use Amazon S3 for static content

Solution

  1. Step 1: Understand region failure scope

    Multi-AZ protects against AZ failure, but not entire region failure.

  2. Step 2: Choose multi-region design

    Deploying in multiple regions with Route 53 routing and health checks ensures availability if one region fails.

  3. Final Answer:

    Deploy instances in multiple regions with Route 53 latency-based routing and health checks -> Option A

  4. Quick Check:

    Multi-region + Route 53 = survive region failure [OK]
Hint: Multi-region with Route 53 handles region failures [OK]
Common Mistakes:
  • Thinking multi-AZ covers region failure
  • Relying on single instance with Auto Scaling
  • Ignoring DNS routing for multi-region failover
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard