High availability configuration in GCP - Time & Space Complexity

Time Complexity: High availability configuration

O(n)

Understanding Time Complexity

When setting up high availability, we want to know how the work grows as we add more resources.

We ask: How does adding more instances affect the number of operations needed?

Scenario Under Consideration

Analyze the time complexity of creating multiple VM instances behind a load balancer.

// Create a managed instance group with N instances
resource "google_compute_instance_template" "template" {
  name_prefix = "instance-template"
  machine_type = "e2-medium"
  disk {
    boot = true
    initialize_params {
      image = "debian-cloud/debian-11"
    }
  }
}

resource "google_compute_instance_group_manager" "igm" {
  name = "instance-group"
  base_instance_name = "instance"
  instance_template = google_compute_instance_template.template.self_link
  target_size = var.instance_count
}

resource "google_compute_backend_service" "backend" {
  name = "backend-service"
  backend {
    group = google_compute_instance_group_manager.igm.instance_group
  }
  load_balancing_scheme = "EXTERNAL"
  protocol = "HTTP"
}

This sequence creates a template, then a group of N instances, and attaches them to a load balancer.

Identify Repeating Operations

Look at what repeats as we increase the number of instances.

• Primary operation: Creating each VM instance in the managed instance group.
• How many times: Once per instance, so N times.
• Load balancer setup happens once, not per instance.

How Execution Grows With Input

Each new instance adds one more creation operation.

Input Size (n)	Approx. Api Calls/Operations
10	About 10 instance creations + 1 load balancer setup
100	About 100 instance creations + 1 load balancer setup
1000	About 1000 instance creations + 1 load balancer setup

Pattern observation: The number of instance creation operations grows directly with the number of instances.

Final Time Complexity

Time Complexity: O(n)

This means the work grows in a straight line as you add more instances.

Common Mistake

[X] Wrong: "Adding more instances only requires a fixed amount of work because the load balancer handles them all at once."

[OK] Correct: Each instance still needs to be created and configured separately, so work grows with the number of instances.

Interview Connect

Understanding how resource creation scales helps you design systems that stay reliable as they grow.

Self-Check

"What if we used a serverless platform instead of VMs? How would the time complexity change?"

Practice

1. What is the main purpose of configuring high availability in a cloud service?

easy

A. To make the service run faster for a single user

B. To reduce the cost of running the service

C. To limit the number of users accessing the service

D. To keep the service running even if some parts fail

Solution

1. Step 1: Understand high availability concept

   High availability means the system stays up and working even if some components fail.

2. Step 2: Identify the main goal

   The goal is to avoid downtime and keep the service accessible to users.

3. Final Answer:

   To keep the service running even if some parts fail -> Option D

4. Quick Check:

   High availability = service stays running despite failures [OK]

Hint: High availability means no downtime during failures [OK]

Common Mistakes:

• Confusing high availability with cost reduction
• Thinking it only improves speed for one user
• Assuming it limits user access

2. Which GCP resource helps automatically replace unhealthy VM instances to maintain high availability?

easy

A. Managed Instance Group with health checks

B. Cloud Storage Bucket

C. Cloud SQL instance

D. Cloud Functions

Solution

1. Step 1: Identify resource for auto healing

   Managed Instance Groups (MIGs) can use health checks to detect unhealthy VMs.

2. Step 2: Understand auto replacement

   MIGs automatically recreate unhealthy instances to keep the service healthy.

3. Final Answer:

   Managed Instance Group with health checks -> Option A

4. Quick Check:

   Auto replace unhealthy VMs = Managed Instance Group + health checks [OK]

Hint: Auto healing uses Managed Instance Groups with health checks [OK]

Common Mistakes:

• Choosing storage or database services instead of compute
• Confusing Cloud Functions with VM management
• Ignoring health checks role

3. Consider a Managed Instance Group spread across two zones with health checks enabled. If one zone fails completely, what happens to the instances?

medium

A. Instances in the failed zone are replaced in the same zone

B. Instances in the failed zone remain down until manual restart

C. Instances in the failed zone are replaced in the other zone

D. All instances in both zones are shut down

Solution

1. Step 1: Understand multi-zone MIG behavior

   MIGs spread instances across zones for fault tolerance.

2. Step 2: Analyze failure impact

   If one zone fails, MIG recreates instances in healthy zones to maintain capacity.

3. Final Answer:

   Instances in the failed zone are replaced in the other zone -> Option C

4. Quick Check:

   Zone failure triggers instance replacement in healthy zones [OK]

Hint: MIGs replace failed zone instances in other zones automatically [OK]

Common Mistakes:

• Thinking instances are replaced in the failed zone
• Assuming manual restart is needed
• Believing all instances shut down

4. You configured a Managed Instance Group with health checks, but unhealthy instances are not being replaced. What is the most likely cause?

medium

A. Autohealing is disabled in the instance group

B. Instances are in multiple zones

C. Health check is not attached to the instance group

D. Firewall rules block all traffic

Solution

1. Step 1: Check health check attachment

   Health checks must be attached to trigger autohealing, but this alone is not enough.

2. Step 2: Verify autohealing setting

   Autohealing must be enabled in the instance group to replace unhealthy instances.

3. Final Answer:

   Autohealing is disabled in the instance group -> Option A

4. Quick Check:

   Autohealing disabled = no instance replacement [OK]

Hint: Autohealing must be enabled to replace unhealthy instances [OK]

Common Mistakes:

• Assuming health check attachment alone triggers replacement
• Blaming multi-zone setup
• Ignoring autohealing configuration

5. You want to design a highly available web application on GCP that remains online even if an entire zone fails. Which combination of configurations best achieves this?

hard

A. Single-zone Managed Instance Group with health checks and autoscaling

B. Multi-zone Managed Instance Group with health checks and autoscaling

C. Single VM instance with a static IP and firewall rules

D. Cloud Storage bucket with versioning enabled

Solution

1. Step 1: Understand zone failure impact

   A single zone failure can take down all instances in that zone if only single-zone is used.

2. Step 2: Choose multi-zone MIG with health checks and autoscaling

   This setup spreads instances across zones, replaces unhealthy ones, and adjusts capacity automatically.

3. Step 3: Evaluate other options

   Single-zone lacks zone failure protection; single VM is a single point of failure; storage bucket is not compute.

4. Final Answer:

   Multi-zone Managed Instance Group with health checks and autoscaling -> Option B

5. Quick Check:

   Multi-zone MIG + health checks + autoscaling = high availability [OK]

Hint: Use multi-zone MIG with health checks and autoscaling for best availability [OK]

Common Mistakes:

• Choosing single-zone MIG ignoring zone failure
• Using single VM which is a single failure point
• Confusing storage bucket with compute resources