October 4, 2004

nginx first public release

Igor Sysoev released nginxA high-performance web server and reverse proxy — event-driven design for massive concurrency. 0.1.0 on October 4, 2004 — an event-driven web server built to solve the C10K concurrency problem.

What it was for

NginxnginxA high-performance web server and reverse proxy — event-driven design for massive concurrency. serves static files, reverse-proxies to app servers (NodeNode.js — JavaScript on the server via an event-driven runtime built on V8., Rails, PHP-FPM), and terminates TLSTransport Layer Security — encryption that protects data in transit on the web and networks. at scale with low memory per connection. It powers CDNs, APIApplication programming interface — a defined way for programs to talk to each other or to a service. gateways, and KubernetesAn orchestration system for containers — schedules, scales, and manages fleets of services in production. ingress controllers. Typical setup: nginxA high-performance web server and reverse proxy — event-driven design for massive concurrency. on port 443 → upstream Puma or uvicorn workers handling dynamic requests.

People

  • Igor Sysoevcreator

Companies

  • Nginx

Why it's here

nginxA high-performance web server and reverse proxy — event-driven design for massive concurrency. challenged Apache's dominance with async I/O and became the default edge server for high-traffic sites.

Why it mattered

It made reverse-proxying and load balancing routine for every backend team.

What it solved

Process-per-connection Apache models struggled past thousands of concurrent clients.

Media

  • Nginx
    ImageNginx

    Igor Sysoev, Public domain, via Wikimedia Commons

Related