Why virtual hosting serves multiple domains in Nginx - Performance Analysis

Time Complexity: Why virtual hosting serves multiple domains

O(n)

Understanding Time Complexity

We want to understand how nginx handles multiple websites using virtual hosting.

Specifically, how the work grows when more domains are added.

Scenario Under Consideration

Analyze the time complexity of this nginx virtual hosting setup.

server {
    listen 80;
    server_name example.com;
    root /var/www/example;
}

server {
    listen 80;
    server_name example.org;
    root /var/www/example_org;
}

server {
    listen 80;
    server_name example.net;
    root /var/www/example_net;
}
    

This config serves three different domains by matching the requested domain name.

Identify Repeating Operations

When a request comes, nginx checks each server block to find a matching domain.

• Primary operation: Comparing the requested domain to each server_name.
• How many times: Once per server block until a match is found or all checked.

How Execution Grows With Input

As the number of domains (server blocks) increases, nginx checks more names.

Input Size (n)	Approx. Operations
10	Up to 10 comparisons
100	Up to 100 comparisons
1000	Up to 1000 comparisons

Pattern observation: The work grows roughly in direct proportion to the number of domains.

Final Time Complexity

Time Complexity: O(n)

This means the time to find the right domain grows linearly as more domains are added.

Common Mistake

[X] Wrong: "nginx instantly knows the right domain no matter how many there are."

[OK] Correct: nginx checks domains one by one until it finds a match, so more domains mean more checks.

Interview Connect

Understanding how nginx matches domains helps you explain real server behavior clearly and confidently.

Self-Check

"What if nginx used a hash map to find domains instead of checking each one? How would the time complexity change?"

Practice

1. What is the main purpose of virtual hosting in nginx?

easy

A. To create backups of website data automatically

B. To increase the server's CPU speed

C. To block unwanted visitors from accessing the server

D. To serve multiple websites from a single server using different domain names

Solution

1. Step 1: Understand virtual hosting concept

   Virtual hosting allows one server to handle many websites by using domain names to select content.

2. Step 2: Identify the main purpose

   This means the server can serve different websites without needing separate servers for each domain.

3. Final Answer:

   To serve multiple websites from a single server using different domain names -> Option D

4. Quick Check:

   Virtual hosting = multiple domains on one server [OK]

Hint: Virtual hosting means many sites, one server [OK]

Common Mistakes:

• Thinking virtual hosting speeds up CPU
• Confusing virtual hosting with backups
• Believing it blocks visitors

2. Which nginx directive is used to specify the domain names for virtual hosting?

easy

A. server_name

B. location

C. listen

D. root

Solution

1. Step 1: Recall nginx configuration directives

   The server_name directive tells nginx which domain names a server block should respond to.

2. Step 2: Match directive to purpose

   Other directives like root set content folder, listen sets port, location defines URL paths.

3. Final Answer:

   server_name -> Option A

4. Quick Check:

   Domain names use server_name [OK]

Hint: Domain names go in server_name directive [OK]

Common Mistakes:

• Using root for domain names
• Confusing listen with domain matching
• Thinking location sets domain

3. Given this nginx server block snippet, what domain will it serve?

server {
  listen 80;
  server_name example.com www.example.com;
  root /var/www/example;
}

medium

A. Only example.com

B. Only www.example.com

C. Both example.com and www.example.com

D. Any domain on port 80

Solution

1. Step 1: Read server_name directive

   The server_name lists both example.com and www.example.com, so nginx matches requests for either domain.

2. Step 2: Understand nginx matching

   Requests to either domain on port 80 will serve content from /var/www/example.

3. Final Answer:

   Both example.com and www.example.com -> Option C

4. Quick Check:

   server_name lists multiple domains = serve all listed [OK]

Hint: server_name can list many domains separated by spaces [OK]

Common Mistakes:

• Assuming only first domain is served
• Thinking root defines domain
• Believing nginx serves all domains by default

4. You configured two server blocks with the same server_name but different root paths. What will happen when a request comes for that domain?

medium

A. nginx will merge both roots and serve combined content

B. nginx will serve content from the first server block it finds

C. nginx will return an error about duplicate server_name

D. nginx will randomly choose one root each time

Solution

1. Step 1: Understand nginx server block matching

   When multiple server blocks have the same server_name, nginx uses the first matching block it finds in the config.

2. Step 2: Result of duplicate server_name

   It does not merge roots or error out; it simply picks the first block, so only one root is used.

3. Final Answer:

   nginx will serve content from the first server block it finds -> Option B

4. Quick Check:

   Duplicate server_name = first block wins [OK]

Hint: Duplicate server_name uses first matching block [OK]

Common Mistakes:

• Expecting nginx to merge content folders
• Thinking nginx throws error on duplicates
• Assuming random selection

5. You want to serve two domains, site1.com and site2.com, on the same nginx server. Which configuration correctly uses virtual hosting to serve different content for each domain?

hard

A. server { listen 80; server_name site1.com; root /var/www/site1; } server { listen 80; server_name site2.com; root /var/www/site2; }

B. server { listen 80; server_name site1.com site2.com; root /var/www/site1; }

C. server { listen 80; server_name site1.com; root /var/www/site1; } server { listen 80; server_name site1.com; root /var/www/site2; }

D. server { listen 80; root /var/www/site1; } server { listen 80; root /var/www/site2; }

Solution

1. Step 1: Check domain to root mapping

   server { listen 80; server_name site1.com; root /var/www/site1; } server { listen 80; server_name site2.com; root /var/www/site2; } uses two server blocks, each with a unique server_name and root folder, correctly separating content by domain.

2. Step 2: Analyze other options

   server { listen 80; server_name site1.com site2.com; root /var/www/site1; } serves both domains from one root, so content is not separated. server { listen 80; server_name site1.com; root /var/www/site1; } server { listen 80; server_name site1.com; root /var/www/site2; } duplicates server_name causing conflict. server { listen 80; root /var/www/site1; } server { listen 80; root /var/www/site2; } lacks server_name, so domains won't be matched properly.

3. Final Answer:

   Two server blocks with distinct server_name and root for each domain -> Option A

4. Quick Check:

   Separate server blocks = separate domains and content [OK]

Hint: Use separate server blocks for each domain with server_name [OK]

Common Mistakes:

• Putting multiple domains in one block with one root
• Duplicating server_name in multiple blocks
• Omitting server_name directive