NGINX, pronounced like “engine-ex”, is an open-source web server that, since its initial success as a web server, is now also used as a reverse proxy, HTTP cache, and load balancer.
Some high-profile companies using NGINX include Autodesk, Atlassian, Intuit, T-Mobile, GitLab, DuckDuckGo, Microsoft, IBM, Google, Adobe, Salesforce, VMWare, Xerox, LinkedIn, Cisco, Facebook, Target, Citrix Systems, Twitter, Apple, Intel, and many more (source).
NGINX was originally created by Igor Sysoev, with its first public release in October 2004. Igor initially conceived the software as an answer to the C10k problem, which is a problem regarding the performance issue of handling 10,000 concurrent connections.
Because its roots are in performance optimization under scale, NGINX often outperforms other popular web servers in benchmark tests, especially in situations with static content and/or high concurrent requests, which is why Kinsta uses NGINX to power its hosting.
How Does NGINX Work?
NGINX is built to offer low memory usage and high concurrency. Rather than creating new processes for each web request, NGINX uses an asynchronous, event-driven approach where requests are handled in a single thread.
With NGINX, one master process can control multiple worker processes. The master maintains the worker processes, while the workers do the actual processing. Because NGINX is asynchronous, each request can be executed by the worker concurrently without blocking other requests.
Some common features seen in NGINX include:
- Reverse proxy with caching
- Load balancing
- FastCGI support with caching
- Handling of static files, index files, and auto-indexing
- TLS/SSL with SNI
NGINX vs Apache Usage Stats
Apache is another popular open-source web server. In terms of raw numbers, Apache is the most popular web server in existence and is used by 47% of all websites with a known web server, according to W3Techs.
While Apache is the most popular overall option, NGINX is actually the most popular web server among high-traffic websites.
When you break down usage rates by traffic, NGINX powers:
- 56.1% of the 100,000 most popular sites
- 63.2% of the 10,000 most popular sites
- 57% of the 1,000 most popular sites
In fact, NGINX is used by some of the most resource-intensive sites in existence, including Netflix, NASA, and even WordPress.com.
Apache’s usage, on the other hand, moves in the opposite direction as a site’s traffic increases. It powers:
- 27.1% of the 100,000 most popular sites
- 21.5% of the 10,000 most popular sites
- 16.2% of the 1,000 most popular sites
If we take a look at Google Search terms since 2004 we can see that Apache has been on a steady decline, while NGINX has seen slight growth.
NGINX vs Apache
Again, when you consider that NGINX performs better under scale, it’s not surprising that high-traffic websites opt for NGINX over Apache.
How to Check If You’re Running NGINX or Apache
On most websites, you can simply check the
server HTTP header to see if it says NGINX or Apache. You can see HTTP headers by launching the network tab in Chrome Devtools. Or you can check headers in a tool like Pingdom or GTmetrix. However, the HTTP header might not always reveal the underlying web server. For example, if your WordPress site is behind a proxy service such as Cloudflare, the
server HTTP header will then say cloudflare instead.
NGINX HTTP Header