Thirty years since the first release
In April 1995 a group of webmasters takes the code of the NCSA httpd server — the most widespread web server of the time, left unmaintained after its author’s departure — and begins collecting and applying patches. The result is Apache HTTP Server, whose name, according to tradition, derives from “a patchy server”. Thirty years later, Apache remains the web server with the largest installed base in the world, present on millions of production servers.
The project is not just software: it is the starting point of the Apache Software Foundation (ASF), founded in 1999 to provide a legal and organisational structure for open source projects. The Apache governance model — meritocratic, consensus-based, with individual rather than corporate contributions — has influenced hundreds of subsequent projects.
Technical evolution
The Apache of 1995 used a prefork model: one process per connection, simple and robust but expensive in terms of resources. Over the years the architecture has evolved through Multi-Processing Modules (MPMs). The worker module introduces threads, reducing memory consumption. The event module, now the default, manages keep-alive connections with dedicated I/O threads, freeing worker threads to process active requests.
HTTP/2 support via mod_http2 brings multiplexing, server push and header compression. mod_proxy and mod_proxy_balancer turn Apache into a reverse proxy and load balancer, a role that today covers a significant portion of installations. mod_security adds an inline web application firewall, inspecting HTTP traffic based on configurable rules.
The Nginx and Caddy challenge
Apache’s market share has declined significantly from its 2005 peak. Nginx, with its event-driven architecture using a single thread per worker, has gained ground in high-traffic deployments where Apache’s concurrent connection model showed limitations. Caddy introduced automatic HTTPS via Let’s Encrypt and a minimalist configuration that reduces the learning curve.
Apache retains advantages in specific scenarios: per-directory configuration via .htaccess, the most extensive module system in the web server ecosystem, and compatibility with legacy applications that depend on mod_php, mod_perl or mod_rewrite.
A foundation that persists
Thirty years on, Apache HTTP Server is no longer the default choice for every new project. But it remains the most configurable web server, with the most extensive documentation and the broadest application compatibility. For many organisations, Apache is not software to replace: it is consolidated infrastructure that continues to work.
Link: httpd.apache.org