Nginx vs Apache comparison - Hands-On Comparison

Nginx vs Apache Comparison

📖 Scenario: You are setting up a web server for a small business website. You want to compare two popular web servers, Nginx and Apache, to understand their basic configuration differences and how they serve web pages.

🎯 Goal: Build simple configuration files for both Nginx and Apache to serve a static HTML page. Learn how to set up the server root, listen on port 80, and serve an index.html file.

📋 What You'll Learn

Create a basic Nginx configuration file to serve static content

Create a basic Apache configuration file to serve static content

Understand the key differences in configuration syntax

Test that both servers serve the index.html page correctly

💡 Why This Matters

🌍 Real World

Web servers like Nginx and Apache are used worldwide to host websites and web applications. Knowing how to configure them is essential for deploying and managing web services.

💼 Career

Many DevOps and system administrator roles require knowledge of web server configuration and management. Understanding Nginx and Apache basics is a key skill for these jobs.

1

Create Nginx configuration file

Create a file named nginx.conf with a server block that listens on port 80, sets the root directory to /var/www/html, and serves index.html as the default file.

Nginx

# Write the Nginx server block configuration here
# Your code here

Hint

Use the server block to define the listening port and root directory. The location / block handles requests to the root URL.

2

Create Apache configuration file

Create a file named apache.conf with a <VirtualHost *:80> block that sets the DocumentRoot to /var/www/html and specifies index.html as the default directory index.

Nginx

# Write the Apache VirtualHost configuration below
# Your code here

Hint

Use the <VirtualHost *:80> block to define the listening port and document root. The DirectoryIndex directive sets the default file.

3

Compare configuration differences

Add comments in both nginx.conf and apache.conf files explaining the key differences: Nginx uses server blocks and directives like listen, root, and location, while Apache uses <VirtualHost> blocks and directives like DocumentRoot and DirectoryIndex.

Nginx

server {
    listen 80;
    root /var/www/html;
    index index.html;

    location / {
        try_files $uri $uri/ =404;
    }
}

# Add comment about Nginx configuration differences here


    DocumentRoot "/var/www/html"
    DirectoryIndex index.html


# Add comment about Apache configuration differences here
# Your code here

Hint

Write simple comments starting with # describing the main configuration style differences.

4

Test serving index.html page

Write two commands: one to start Nginx using nginx.conf and one to start Apache using apache.conf. Then write a command to fetch the homepage from localhost using curl. Print the output of the curl command.

Nginx

# Start Nginx and Apache, then fetch homepage with curl
# Your code here

Hint

Use sudo nginx -c nginx.conf to start Nginx with your config, sudo apachectl -f apache.conf to start Apache, and curl http://localhost to fetch the homepage.

Practice

1. Which web server is known for using fewer resources and handling many connections efficiently?

easy

A. IIS

B. Apache

C. Nginx

D. Tomcat

Solution

1. Step 1: Understand resource usage

   Nginx is designed to use less memory and CPU by handling many connections asynchronously.

2. Step 2: Compare with Apache

   Apache uses more resources because it creates a new process or thread per connection, which is less efficient.

3. Final Answer:

   Nginx -> Option C

4. Quick Check:

   Low resource use = Nginx [OK]

Hint: Nginx = efficient, Apache = flexible [OK]

Common Mistakes:

• Confusing Apache as more efficient
• Thinking IIS or Tomcat are similar to Nginx
• Assuming all web servers use same resources

2. Which of the following is the correct way to start the Nginx service on a Linux system using systemd?

easy

A. systemctl start nginx

B. nginx start

C. service nginx start

D. start nginx

Solution

1. Step 1: Identify systemd command

   Modern Linux systems use systemctl to manage services.

2. Step 2: Correct syntax for starting Nginx

   The command is systemctl start nginx to start the Nginx service.

3. Final Answer:

   systemctl start nginx -> Option A

4. Quick Check:

   Use systemctl for services [OK]

Hint: Use systemctl to manage services on modern Linux [OK]

Common Mistakes:

• Using old service command on systemd systems
• Typing nginx start which is invalid
• Using start nginx which is not a command

3. Given the following Nginx and Apache configurations, which server will handle 10,000 simultaneous connections more efficiently?

# Nginx: event-driven, asynchronous handling
# Apache: process/thread per connection model

medium

A. Nginx will handle better due to asynchronous event-driven model

B. Neither can handle that many connections

C. Both handle equally well

D. Apache will handle better due to process isolation

Solution

1. Step 1: Understand connection handling models

   Nginx uses an event-driven, asynchronous model that handles many connections with fewer resources.

2. Step 2: Compare Apache's model

   Apache creates a new process or thread per connection, which uses more memory and CPU, limiting scalability.

3. Final Answer:

   Nginx will handle better due to asynchronous event-driven model -> Option A

4. Quick Check:

   Event-driven = better for many connections [OK]

Hint: Event-driven servers handle many connections efficiently [OK]

Common Mistakes:

• Assuming process isolation means better performance
• Thinking Apache scales as well as Nginx
• Ignoring resource limits on Apache

4. You configured Apache to serve static files but notice high CPU usage under load. What is a likely cause compared to Nginx?

medium

A. Apache caches static files inefficiently

B. Apache uses more CPU because it creates a process per request

C. Nginx does not support static files

D. Apache does not support HTTP/1.1

Solution

1. Step 1: Analyze Apache's process model

   Apache creates a new process or thread for each request, increasing CPU usage under load.

2. Step 2: Compare with Nginx's approach

   Nginx uses an event-driven model that handles many requests with fewer processes, reducing CPU load.

3. Final Answer:

   Apache uses more CPU because it creates a process per request -> Option B

4. Quick Check:

   Process per request = higher CPU [OK]

Hint: Process per request = more CPU usage [OK]

Common Mistakes:

• Thinking Apache caches static files poorly
• Believing Nginx lacks static file support
• Incorrectly assuming Apache lacks HTTP/1.1 support

5. You want to serve a high-traffic website with many simultaneous users and low memory usage. Which setup is best and why?

hard

A. Use Nginx only as a reverse proxy, Apache for static files

B. Use Apache with many worker processes for flexibility

C. Use Apache with default prefork module for stability

D. Use Nginx for event-driven handling and low memory use

Solution

1. Step 1: Identify requirements

   High traffic and low memory use require efficient connection handling and low resource consumption.

2. Step 2: Evaluate server models

   Nginx uses an event-driven model that handles many connections with low memory, ideal for high traffic.

3. Step 3: Compare other options

   Apache with many workers uses more memory; prefork is stable but heavy; using Nginx only as proxy adds complexity.

4. Final Answer:

   Use Nginx for event-driven handling and low memory use -> Option D

5. Quick Check:

   Event-driven + low memory = Nginx best [OK]

Hint: For high traffic and low memory, choose Nginx [OK]

Common Mistakes:

• Choosing Apache for low memory use
• Ignoring Nginx's event-driven advantage
• Overcomplicating with mixed setups