Skip to content

The Web Server Wars: Apache to Nginx

Abstract

The program that answers when a browser asks for a page has changed hands three times. NCSA HTTPd, written by a student in Illinois in 1993, was abandoned by its author within a year; its users pooled their patches and called the result Apache, which led the Netcraft survey from April 1996 for roughly two decades. Microsoft’s IIS came within six points of it in 2014 and then faded. The server that finally passed Apache was Nginx, written by a Russian system administrator in his spare time from 2002 to cope with ten thousand simultaneous connections.

NCSA HTTPd

The first web server was the one Tim Berners-Lee wrote at CERN. The first popular one came from the same place as the first popular browser. At the National Center for Supercomputing Applications in Illinois, while the Mosaic team wrote the client, an undergraduate named Rob McCool wrote the server, NCSA HTTPd, first released in 1993. It was free, it was in the public domain, and it introduced the Common Gateway Interface (CGI), the convention that let a server run a program to produce a page instead of reading a file.

In mid-1994 McCool left NCSA, and development stalled. The server was by then the most widely used on the web, and the people running it kept fixing it on their own. Each site had its own collection of bug fixes and extensions, and no one to send them to.

The Apache Group

In February 1995 a handful of these webmasters began to coordinate by email. Brian Behlendorf, who ran the web server at HotWired, and Cliff Skolnick set up a mailing list and a shared machine in the San Francisco Bay Area, with bandwidth donated by HotWired. By the end of the month eight people formed the original Apache Group: Behlendorf, Roy Fielding, Rob Hartill, David Robinson, Skolnick, Randy Terbush, Robert Thau, and Andrew Wilson.

They took NCSA HTTPd 1.3, applied the accumulated fixes, and released the result as Apache 0.6.2 in April 1995. Over May and June, Thau redesigned the internals under the code name Shambhala, with a module interface and a pool of pre-started worker processes. Apache 1.0 came out on 1 December 1995. By April 1996, according to the Netcraft survey, it was the most widely used web server on the internet. In June 1999 the group incorporated as the Apache Software Foundation, which later became the home of hundreds of unrelated projects (see The Open Source Movement).

Myth: Apache is named after “a patchy server”

The story that the name is a pun on the patches applied to NCSA’s code is the best-known etymology in open-source software, and the project’s FAQ of the 1990s told it: “A cute name which stuck. Apache is ‘A PAtCHy server’.” Behlendorf, who first used the name, said in a 2000 interview that he chose it for its “take no prisoners” sound and that another list member then pointed out the pun; in a 2007 interview he gave the patches as the reason. The Apache Software Foundation’s current account is that the name shows appreciation for the Apache people and that the pun “quickly spread amongst members of the community” until “rumor became lore, and lore became legend”. The pun is real and early; whether it was the reason for the name, its own coiner has answered both ways. See Myths and Misconceptions.

Apache won because it ran everywhere, cost nothing, and could be extended by modules. The combination with Linux, MySQL, and PHP became the default way to build a website for a decade.

Microsoft’s Server

Microsoft’s first web server was a freeware research project from the European Microsoft Windows NT Academic Centre at the University of Edinburgh. It could not carry the traffic of microsoft.com, so the company wrote its own, Internet Information Server. Version 1.0 was a free add-on for Windows NT 3.51, and from Windows NT 4.0 in 1996 it was in the box, the server-side counterpart of the bundling strategy in the browser wars. Version 3.0 added Active Server Pages.

Being installed by default on every Windows server made IIS common and made it a target. In July 2001 the Code Red worm spread through a buffer overflow in IIS 4 and 5; IIS 6, shipped with Windows Server 2003, came with a new process model and a much smaller default configuration. Among sites counted by Netcraft, IIS reached 32.80 percent in February 2014 against Apache’s 38.22, the closest it came. By November 2026, W3Techs measured it at 2.8 percent.

Ten Thousand Connections

Apache’s classic design gave each connection its own process or thread. This is simple and robust, and it works well while the number of simultaneous clients is in the hundreds. In 1999 the engineer Dan Kegel put up a web page that began, “It’s time for web servers to handle ten thousand clients simultaneously, don’t you think?” He called it the C10k problem. The hardware was not the obstacle: Kegel worked out that a $1,200 machine had enough memory and network capacity for twenty thousand clients. The obstacle was the one-process-per-client model, in which ten thousand mostly idle connections meant ten thousand stacks and constant context switching. The alternative was a single process watching all its connections through the operating system’s event notification interfaces and doing work only when one of them had data.

Nginx

Igor Sysoev was a system administrator at Rambler, a Russian search engine and portal, and C10k was his daily problem. In 2002 he began writing a server built on an event loop from the start: a few worker processes, each handling thousands of connections, with memory use that barely moved as connections were added. He wrote it outside his official duties. The first public release of Nginx (pronounced “engine x”) came on 4 October 2004.

It spread first among busy Russian sites and then among Western ones that had outgrown Apache. Many put Nginx in front of Apache as a reverse proxy, letting it hold the slow client connections and serve static files while Apache ran the application. Apache answered with an event-driven mode of its own in version 2.4, but the default had shifted.

In July 2011 Sysoev and Maxim Konovalov founded Nginx, Inc. to sell support and, from 2013, a paid edition. On 11 March 2019 the American networking company F5 bought it for $670 million.

The Raid

Nine months after the sale, on 12 December 2019, Russian police searched Nginx’s Moscow office and questioned Sysoev and Konovalov. The Rambler group, by then part-owned by the state bank Sberbank, claimed that because Sysoev had written Nginx while he was its employee, the code and the $670 million belonged to Rambler. Sysoev had always said that he wrote it in his own time and that server software was not part of his job. Within days, after an outcry in the Russian technology industry, Sberbank called a special board meeting to stop the criminal complaint, and Rambler dropped it.

Sysoev left F5 in January 2022. Former colleagues released a fork called Angie later that year, and in February 2024 the long-time core developer Maxim Dounin started another, freenginx, saying that F5’s management was interfering with decisions that belonged to the developers. A program written to escape one employer’s claim now exists in three versions, each controlled by different people.

The Count

In August 2020 Netcraft found Nginx on more web-facing computers than any other server, 34.10 percent against Apache’s 33.57. In W3Techs’ figures for November 2026, Nginx ran 29.8 percent of websites whose server is known and Apache 20.5. The server in first place, at 34.5 percent, was neither: it was Cloudflare’s, the front end of a content delivery network. For a growing share of the web, the machine that answers the browser no longer belongs to the site.

πŸ“š Sources