Don't Panic — NGINX Fundamentals

NGINX is the bouncer, receptionist, and courier standing in front of a web application. A request arrives, NGINX reads its rulebook, and it either serves a file or forwards the request to a backend. Before this style of server, a common approach gave each connection its own process or thread. That works until a great many slow connections arrive and begin consuming the furniture.

The important machinery is the master process and its workers. The master reads the configuration, opens the listening sockets, and manages workers. The workers handle connections through event loops, each keeping many conversations moving without waiting for one sleepy client to finish a sentence. This is why a small worker set can carry a large number of connections, provided the operating system also allows enough open files.

The rulebook is a tree, which is NGINX's polite way of admitting that its configuration has geography. The main, events, and http contexts set the terrain. A server block chooses a virtual server from the connection address, port, and Host header. A location block then chooses what to do with the request URI: serve a file, hand it to an application, redirect it, or return an error.

Here is the surprise that earns its keep. A broad location is not necessarily the winner. NGINX checks an exact match first, remembers the longest prefix, and can then let the first matching regular expression take over. The ^~ modifier changes that result. When a request seems to be obeying a different rule than the one underlined on your screen, it is usually following this selection path with unnerving literalness.

Configuration changes are less dramatic than they look. A reload has the master check the new configuration first. If it is invalid, the old configuration keeps serving traffic. If it is valid, new workers start and old workers finish their current work. That is a graceful handoff, not sorcery, although it is acceptable to appreciate the distinction.

Read the Intro when you need the full architecture and request path. Use Slides for the selection flow and context map. Keep the Cheatsheet nearby when root, alias, try_files, or a location modifier appears in a configuration review. The Practice tab turns that map into requests you can observe, while the next NGINX courses take the proxy, load-balancing, and security branches beyond this foundation.

Don't Panic — NGINX Fundamentals

Relevant careers