Comparing the best web servers: Caddy, Apache, and Nginx

• Caddy

  403 53,904 9.5 Go

  Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS

  

Installing Caddy is quite straightforward. Simply download the static binary for your preferred platform on GitHub or follow the instructions on the installation document. To launch the Caddy server daemon, run caddy run in the terminal. However, nothing will happen without a configuration file.

• Nginx

  99 20,257 8.8 C

  An official read-only mirror of http://hg.nginx.org/nginx/ which is updated hourly. Pull requests on GitHub cannot be accepted and will be automatically closed. The proper way to submit changes to nginx is via the nginx development mailing list, see http://nginx.org/en/docs/contributing_changes.html

  

With origins tracing back to the C10K problem, which refers to a web server’s inability to support more than 10,000 concurrent users, Nginx was developed with performance in mind. One of its original goals focused on speed, an area in which Apache was believed to be lacking.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• Apache

  82 3,428 9.3 C

  Mirror of Apache HTTP Server. Issues: http://issues.apache.org

  

The Apache HTTP Server, maintained by the Apache Software Foundation, was released in 1995, quickly becoming the world’s favorite web server. Most often used as part of the LAMP stack, Linux, Apache, MySQL, and PHP, Apache is available for both Unix and Windows operating systems.

Suggest a related project