Understanding Nginx Architecture: Core, Modules, and Request Flow
This article explains Nginx’s lightweight kernel and modular design, detailing how the core, basic, and third‑party modules are organized by structure and function, and describing the roles of handlers, filters, and proxies in processing HTTP requests and responses.
Nginx consists of a kernel and modules.
The kernel is designed to be tiny and simple; it merely maps client requests to a location block by reading the configuration file, and each directive in that location triggers a different module to perform its task.
Nginx’s power comes from its many modules. Nginx includes numerous built‑in modules, and users can develop custom modules as needed.
Modules can be classified by structure:
Core modules, such as the HTTP, EVENT, and MAIL modules.
Basic modules, such as HTTP Access, HTTP FastCGI, HTTP Proxy, and HTTP Rewrite modules.
Third‑party modules, such as HTTP Upstream RequestHash, Notice, HTTP Access Key, and user‑defined modules.
Modules can also be classified by function:
Handlers – modules that directly process requests, generate output, and modify header information; typically only one handler is present.
Filters – modules that modify the output produced by handlers before Nginx sends the response.
Proxies – modules that act as upstream clients (e.g., FastCGI) to interact with backend services, providing proxying and load‑balancing capabilities.
Nginx module HTTP request and response process:
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Java High-Performance Architecture
Sharing Java development articles and resources, including SSM architecture and the Spring ecosystem (Spring Boot, Spring Cloud, MyBatis, Dubbo, Docker), Zookeeper, Redis, architecture design, microservices, message queues, Git, etc.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.