Why load balancing matters in Azure - Performance Analysis

Time Complexity: Why load balancing matters

O(n)

Understanding Time Complexity

We want to understand how the work done by load balancing changes as more users or requests come in.

How does the system handle growing traffic efficiently?

Scenario Under Consideration

Analyze the time complexity of distributing incoming requests to backend servers.

// Azure Load Balancer example
resource lb 'Microsoft.Network/loadBalancers@2022-05-01' = {
  name: 'myLoadBalancer',
  location: resourceGroup().location,
  properties: {
    frontendIPConfigurations: [
      {
        name: 'LoadBalancerFrontEnd',
        properties: { publicIPAddress: { id: publicIP.id } }
      }
    ],
    backendAddressPools: [ { name: 'BackendPool' } ],
    loadBalancingRules: [
      {
        name: 'HTTPRule',
        properties: {
          frontendIPConfiguration: { id: lb.properties.frontendIPConfigurations[0].id },
          backendAddressPool: { id: lb.properties.backendAddressPools[0].id },
          protocol: 'Tcp',
          frontendPort: 80,
          backendPort: 80,
          enableFloatingIP: false,
          idleTimeoutInMinutes: 4,
          loadDistribution: 'Default'
        }
      }
    ]
  }
}

This setup distributes incoming web requests evenly across multiple servers.

Identify Repeating Operations

Look at what happens repeatedly as requests come in.

• Primary operation: Routing each incoming request to one backend server.
• How many times: Once per request, no matter how many requests arrive.

How Execution Grows With Input

Each new request causes one routing decision by the load balancer.

Input Size (n)	Approx. Api Calls/Operations
10	10 routing operations
100	100 routing operations
1000	1000 routing operations

Pattern observation: The number of routing operations grows directly with the number of requests.

Final Time Complexity

Time Complexity: O(n)

This means the work done by the load balancer grows linearly as more requests come in.

Common Mistake

[X] Wrong: "Load balancing handles all requests instantly, so time doesn't grow with more users."

[OK] Correct: Each request still needs to be routed, so the total work grows as requests increase, even if each routing is fast.

Interview Connect

Understanding how load balancing scales helps you design systems that stay responsive as more people use them.

Self-Check

"What if the load balancer had to check the health of each backend server before routing every request? How would the time complexity change?"

Practice

1. Why is load balancing important in Azure cloud services?

easy

A. It stores user data securely in the cloud.

B. It automatically updates the operating system on servers.

C. It spreads user traffic across servers to keep apps fast and reliable.

D. It creates backups of all user files daily.

Solution

1. Step 1: Understand load balancing purpose

   Load balancing distributes incoming user requests across multiple servers to avoid overload on any single server.

2. Step 2: Identify benefits in Azure context

   This distribution keeps applications fast and available, even if one server fails.

3. Final Answer:

   It spreads user traffic across servers to keep apps fast and reliable. -> Option C

4. Quick Check:

   Load balancing = traffic spread for speed and reliability [OK]

Hint: Load balancing means sharing traffic to avoid slowdowns [OK]

Common Mistakes:

• Confusing load balancing with data storage
• Thinking it updates software automatically
• Assuming it handles backups

2. Which of the following is required to set up an Azure Load Balancer?

easy

A. A public IP address and a resource group

B. A virtual machine scale set only

C. An Azure SQL database

D. A storage account with blobs

Solution

1. Step 1: Identify Azure Load Balancer requirements

   Azure Load Balancer needs a public IP address to receive traffic and a resource group to organize resources.

2. Step 2: Eliminate unrelated options

   Virtual machine scale sets, SQL databases, and storage accounts are not mandatory for basic load balancer setup.

3. Final Answer:

   A public IP address and a resource group -> Option A

4. Quick Check:

   Load balancer setup = public IP + resource group [OK]

Hint: Load balancer needs public IP and resource group [OK]

Common Mistakes:

• Choosing VM scale set as mandatory
• Confusing with database or storage requirements
• Ignoring the need for a public IP

3. Consider this Azure Load Balancer setup: Two servers receive traffic equally. If one server fails, what happens to incoming requests?

medium

A. Users get an error page immediately.

B. All traffic stops until the failed server is fixed.

C. Traffic is split randomly, including the failed server.

D. Traffic automatically routes only to the healthy server.

Solution

1. Step 1: Understand load balancer health monitoring

   Azure Load Balancer checks server health and stops sending traffic to unhealthy servers.

2. Step 2: Predict traffic routing on failure

   When one server fails, the load balancer routes all traffic to the healthy server automatically.

3. Final Answer:

   Traffic automatically routes only to the healthy server. -> Option D

4. Quick Check:

   Load balancer avoids failed servers for traffic [OK]

Hint: Load balancer sends traffic only to healthy servers [OK]

Common Mistakes:

• Assuming traffic stops completely
• Thinking traffic still goes to failed server
• Believing users see errors immediately

4. You configured an Azure Load Balancer but users report slow app response. What is a likely configuration mistake?

medium

A. Setting the load balancer to distribute traffic evenly

B. Not assigning a public IP to the load balancer

C. Using too many backend servers

D. Enabling health probes for backend servers

Solution

1. Step 1: Check load balancer public IP assignment

   Without a public IP, the load balancer cannot receive external traffic, causing slow or no responses.

2. Step 2: Review other options

   Using many servers or even traffic distribution is normal; health probes improve reliability.

3. Final Answer:

   Not assigning a public IP to the load balancer -> Option B

4. Quick Check:

   Missing public IP causes traffic issues [OK]

Hint: Load balancer needs public IP to receive traffic [OK]

Common Mistakes:

• Blaming too many servers for slowness
• Thinking even traffic distribution causes slow response
• Ignoring the importance of health probes

5. You want to ensure your Azure app stays online even if one server fails. Which load balancing strategy best supports this?

hard

A. Distribute traffic evenly with health probes to detect failures

B. Send all traffic to a single server for simplicity

C. Use a load balancer without health probes

D. Manually switch traffic between servers when one fails

Solution

1. Step 1: Identify strategy for high availability

   Even traffic distribution with health probes ensures traffic only goes to healthy servers, keeping the app online.

2. Step 2: Evaluate other options

   Sending all traffic to one server risks downtime; no health probes means failures go undetected; manual switching is slow and error-prone.

3. Final Answer:

   Distribute traffic evenly with health probes to detect failures -> Option A

4. Quick Check:

   Even distribution + health probes = high availability [OK]

Hint: Use health probes to avoid failed servers automatically [OK]

Common Mistakes:

• Relying on single server for all traffic
• Ignoring health probes in load balancer
• Trying manual traffic switching