Event-driven architecture in Nginx - Mini Project: Build & Apply

Basic Event-Driven Architecture with Nginx

📖 Scenario: You are setting up a simple web server using Nginx that responds differently based on specific events (HTTP requests to different URLs). This simulates an event-driven architecture where Nginx acts on events (requests) to serve different content.

🎯 Goal: Build an Nginx configuration that listens on port 8080 and serves different responses for two URL paths: /event1 and /event2. Each path should return a unique message, demonstrating how Nginx handles events differently.

📋 What You'll Learn

Create a basic Nginx server block listening on port 8080

Add location blocks for /event1 and /event2

Configure each location to return a distinct plain text message

Test the configuration by printing the response for each event URL

💡 Why This Matters

🌍 Real World

Web servers often handle different requests as events and respond accordingly. This project shows how Nginx can be configured to react to different URL events with specific responses.

💼 Career

Understanding how to configure Nginx for event-driven responses is useful for DevOps roles managing web infrastructure and optimizing server behavior.

1

Create the basic Nginx server block

Write an Nginx server block that listens on port 8080 and has a root directory set to /var/www/html.

Nginx

# Your code here
# Create a server block listening on port 8080 with root /var/www/html

Need a hint?

Use server {} block with listen 8080; and root /var/www/html; inside.

2

Add location blocks for event URLs

Inside the existing server block, add two location blocks: one for /event1 and one for /event2.

Nginx

server {
    listen 8080;
    root /var/www/html;

    # Add location blocks for /event1 and /event2 here
    # Your code here
}

Need a hint?

Use location /event1 {} and location /event2 {} inside the server block.

3

Configure responses for each event location

Inside the /event1 location block, add a directive to return the plain text message Event 1 triggered with HTTP status 200. Similarly, inside the /event2 location block, return Event 2 triggered with status 200.

Nginx

server {
    listen 8080;
    root /var/www/html;

    location /event1 {
        # Return 'Event 1 triggered' with status 200
        # Your code here
    }

    location /event2 {
        # Return 'Event 2 triggered' with status 200
        # Your code here
    }
}

Need a hint?

Use the return directive inside each location block to send the message and status.

4

Test the Nginx configuration output

Simulate testing by printing the expected response messages for /event1 and /event2 URLs. Write two print statements that output exactly Event 1 triggered and Event 2 triggered respectively.

Nginx

# Print the expected responses for /event1 and /event2
# Your code here

Need a hint?

Use two print statements, one for each event message.