Unlocking Nginx: Deep Dive into Architecture, Modules, and Event‑Driven Design

1. Introduction

Nginx (pronounced "Engine X") is a free, open‑source, high‑performance HTTP server and reverse proxy, also supporting IMAP, POP3, and SMTP. It can host static sites, act as a reverse proxy, load balancer, and HTTP cache.

2. Key Features of Nginx

Cross‑platform: runs on most Unix‑like systems and has a Windows port.

Simple configuration: easy to learn and use.

Non‑blocking, high‑concurrency: supports tens of thousands of concurrent connections; official tests show 50k, real‑world 20‑30k.

No long‑living connections needed between Nginx and backend servers.

Asynchronous request reception reduces backend load.

Response streaming: sends data to clients while receiving from backends.

Low network dependency: can load‑balance as long as the host is reachable.

Built‑in health checks: detects backend failures via status codes or timeouts.

Low memory usage, cost‑effective, bandwidth‑saving, and highly stable.

3. Overall Architecture

1. Modular Design – Nginx workers contain core and functional modules. Core modules run the event loop and handle networking, storage, and filtering. The modular code allows selective compilation of needed features.

2. Proxy Design – Nginx acts as a high‑performance proxy for HTTP, FastCGI, Memcache, Redis, etc., making proxying a core capability.

3. Event‑Driven Model – An asynchronous, non‑blocking event‑driven architecture enables high concurrency, leveraging OS mechanisms such as epoll, kqueue, and event ports.

4. Master Process Model – The master process handles configuration loading, worker startup, and graceful upgrades; it does not process network traffic.

5. Worker Process Model – Worker processes handle actual network requests; multiple workers can each manage thousands of connections.

4. Modular Design Details

Nginx is built from distinct modules that follow the principle of high cohesion and low coupling.

Core modules : essential for logging, configuration parsing, event handling, and process management.

Standard HTTP modules : provide basic HTTP protocol handling, port configuration, encoding, and header management.

Optional HTTP modules : extend functionality (e.g., Flash streaming, GeoIP, compression, SSL).

Mail service modules : support POP3, IMAP, and SMTP.

Third‑party modules : add custom features such as JSON handling or Lua scripting.

5. Proxy Design: Forward and Reverse Proxy

Forward proxy operates on the client side, forwarding requests to external servers (e.g., GoAgent). Reverse proxy operates on the server side, receiving client requests and forwarding them to backend servers; Nginx itself is a reverse proxy.

6. Event‑Driven Model

The model consists of an event sender, collector, and processor. I/O events are dispatched to the processor, which handles them using multiplexing methods such as select, poll, or epoll.

Event sender: pushes I/O events to the processor.

Event collector: gathers I/O requests from workers.

Event processor: responds to the collected events.

7. Request Processing Mechanisms

Multi‑process mechanism – The master process forks worker processes; each worker handles client connections independently, avoiding lock contention and improving fault tolerance.

Asynchronous non‑blocking mechanism – Workers use async I/O to handle multiple client requests simultaneously; when an I/O operation cannot complete immediately, the worker proceeds to other tasks, and the client is not blocked.

8. Process Model

Nginx employs a master/worker multi‑process architecture. The master starts, forks workers, and manages signals. Workers share a listening socket; only one worker acquires the accept mutex to accept a new connection, ensuring a single process handles each request.

It is recommended that the number of worker processes matches the number of CPU cores to minimize context switching and maximize cache efficiency.

9. Conclusion

This article gives a complete picture of Nginx’s architecture, including its modular design, multi‑process and asynchronous processing, event‑driven model, and proxy capabilities, providing a solid foundation for anyone learning or working with Nginx.