Blue-green deployment routing in Nginx - Time & Space Complexity

Time Complexity: Blue-green deployment routing

O(n)

Understanding Time Complexity

We want to understand how the routing decisions in blue-green deployment scale as requests increase.

How does nginx handle routing when switching between two versions of an app?

Scenario Under Consideration

Analyze the time complexity of the following nginx routing configuration for blue-green deployment.

upstream blue {
    server 10.0.0.1:8080;
}

upstream green {
    server 10.0.0.2:8080;
}

server {
    listen 80;
    location / {
        if ($cookie_version = "blue") {
            proxy_pass http://blue;
        }
        if ($cookie_version = "green") {
            proxy_pass http://green;
        }
    }
}
    

This code routes user requests to either the blue or green server based on a cookie value.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: nginx checks the cookie value for each incoming request.
• How many times: once per request, no loops or recursion inside the config.

How Execution Grows With Input

Each new request triggers a single cookie check and routing decision.

Input Size (n)	Approx. Operations
10	10 cookie checks and routing decisions
100	100 cookie checks and routing decisions
1000	1000 cookie checks and routing decisions

Pattern observation: The work grows linearly with the number of requests.

Final Time Complexity

Time Complexity: O(n)

This means the routing work increases directly with the number of requests.

Common Mistake

[X] Wrong: "Routing decisions take constant time regardless of request count."

[OK] Correct: Each request requires a routing check, so total work grows with requests, not fixed.

Interview Connect

Understanding how routing scales helps you explain real deployment strategies clearly and confidently.

Self-Check

What if we added more versions (blue, green, yellow, etc.)? How would the time complexity change?

Practice

1. What is the main purpose of using blue-green deployment routing with Nginx?

easy

A. To encrypt traffic between client and server

B. To increase the number of servers in the cluster

C. To cache static files for faster loading

D. To switch traffic between two app versions without downtime

Solution

1. Step 1: Understand blue-green deployment concept

   Blue-green deployment uses two versions of an app (blue and green) to switch traffic smoothly.

2. Step 2: Identify Nginx role in routing

   Nginx switches traffic by changing proxy_pass between blue and green upstreams, avoiding downtime.

3. Final Answer:

   To switch traffic between two app versions without downtime -> Option D

4. Quick Check:

   Blue-green routing = traffic switch without downtime [OK]

Hint: Blue-green means two versions, switch traffic smoothly [OK]

Common Mistakes:

• Confusing blue-green with load balancing
• Thinking it increases server count automatically
• Assuming it handles encryption or caching

2. Which Nginx directive is used to switch traffic between blue and green app versions in blue-green deployment?

easy

A. proxy_pass

B. listen

C. server_name

D. root

Solution

1. Step 1: Identify directive for routing requests

   The proxy_pass directive tells Nginx where to send incoming requests.

2. Step 2: Understand blue-green switching

   Switching proxy_pass between blue and green upstream blocks changes the app version served.

3. Final Answer:

   proxy_pass -> Option A

4. Quick Check:

   proxy_pass switches traffic in blue-green [OK]

Hint: proxy_pass directs traffic to app versions [OK]

Common Mistakes:

• Using listen to switch app versions
• Confusing server_name with routing
• Using root which sets document root, not proxy

3. Given this Nginx config snippet, what backend will receive traffic?

upstream blue {
  server 10.0.0.1:8080;
}
upstream green {
  server 10.0.0.2:8080;
}
server {
  listen 80;
  location / {
    proxy_pass http://green;
  }
}

medium

A. 10.0.0.1:8080 (blue)

B. 10.0.0.2:8080 (green)

C. Both blue and green servers

D. No backend, config error

Solution

1. Step 1: Check proxy_pass target

   The proxy_pass points to http://green, so traffic goes to green upstream.

2. Step 2: Identify green upstream server

   Green upstream has server 10.0.0.2:8080, so this server receives traffic.

3. Final Answer:

   10.0.0.2:8080 (green) -> Option B

4. Quick Check:

   proxy_pass to green = 10.0.0.2:8080 [OK]

Hint: proxy_pass target = backend server [OK]

Common Mistakes:

• Assuming traffic goes to blue by default
• Thinking both upstreams get traffic simultaneously
• Believing config has syntax errors

4. Identify the error in this Nginx blue-green deployment config snippet:

upstream blue {
  server 10.0.0.1:8080;
}
upstream green {
  server 10.0.0.2:8080
}
server {
  listen 80;
  location / {
    proxy_pass http://blue;
  }
}

medium

A. Missing semicolon after green server line

B. proxy_pass should use https instead of http

C. listen directive must specify IP address

D. upstream block names must be uppercase

Solution

1. Step 1: Check upstream block syntax

   The green upstream server line lacks a semicolon at the end, causing syntax error.

2. Step 2: Validate other directives

   proxy_pass with http is valid; listen can omit IP; upstream names can be lowercase.

3. Final Answer:

   Missing semicolon after green server line -> Option A

4. Quick Check:

   Missing semicolon causes config error [OK]

Hint: Check semicolons after each directive line [OK]

Common Mistakes:

• Assuming http must be https in proxy_pass
• Thinking listen needs IP address
• Believing upstream names must be uppercase

5. You want to switch live traffic from blue to green app version with zero downtime using Nginx. Which is the best approach?

hard

A. Stop blue servers and start green servers without changing Nginx

B. Change DNS to point to green servers and wait for propagation

C. Change proxy_pass in Nginx config from blue to green and reload Nginx

D. Restart Nginx without changing config to refresh connections

Solution

1. Step 1: Understand zero downtime switch

   Changing proxy_pass in Nginx config directs traffic to green without downtime.

2. Step 2: Reload Nginx to apply changes

   Reloading Nginx applies new config smoothly without dropping connections.

3. Final Answer:

   Change proxy_pass in Nginx config from blue to green and reload Nginx -> Option C

4. Quick Check:

   proxy_pass switch + reload = zero downtime [OK]

Hint: Switch proxy_pass and reload Nginx for smooth update [OK]

Common Mistakes:

• Stopping blue servers causes downtime
• Relying on DNS changes delays switch
• Restarting Nginx without config change does nothing