VNet peering for connectivity in Azure - Time & Space Complexity

Time Complexity: VNet peering for connectivity

O(n²)

Understanding Time Complexity

When connecting two virtual networks using VNet peering, it's important to understand how the number of connections affects the work Azure does behind the scenes.

We want to know how the effort grows as we add more peerings.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// Create VNet peering between two VNets
az network vnet peering create \
  --name Peer1to2 \
  --resource-group MyResourceGroup \
  --vnet-name VNet1 \
  --remote-vnet /subscriptions/{subscriptionId}/resourceGroups/MyResourceGroup/providers/Microsoft.Network/virtualNetworks/VNet2 \
  --allow-vnet-access

// Create VNet peering from VNet2 back to VNet1
az network vnet peering create \
  --name Peer2to1 \
  --resource-group MyResourceGroup \
  --vnet-name VNet2 \
  --remote-vnet /subscriptions/{subscriptionId}/resourceGroups/MyResourceGroup/providers/Microsoft.Network/virtualNetworks/VNet1 \
  --allow-vnet-access

This sequence sets up two-way peering between two virtual networks to enable connectivity.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Creating a VNet peering connection via Azure API.
• How many times: Twice per pair of VNets (one peering each direction).

How Execution Grows With Input

Each new VNet added requires peering with existing VNets, doubling the number of peering connections needed.

Input Size (n)	Approx. Api Calls/Operations
2 VNets	2 peerings (one each direction)
3 VNets	6 peerings (each pair peered both ways)
4 VNets	12 peerings

Pattern observation: The number of peering operations grows quickly as more VNets are connected, roughly proportional to the square of the number of VNets.

Final Time Complexity

Time Complexity: O(n²)

This means that as you add more virtual networks, the number of peering connections you need grows much faster, roughly like the square of the number of networks.

Common Mistake

[X] Wrong: "Adding one more VNet only adds one more peering connection."

[OK] Correct: Each new VNet must peer with all existing VNets, so the number of connections grows much faster than just one per new network.

Interview Connect

Understanding how network connections scale helps you design cloud networks that stay manageable and efficient as they grow.

Self-Check

What if VNet peering allowed automatic transitive connectivity? How would the time complexity of setting up connections change?