You can also see some configurations that run both - it’s all up to you as the admin. However, most benchmarks have clocked NGINX at serving websites faster. Apache is included with all major Linux distributions and requires much less configuration. Here’s a good rule of thumb: If you want to run ONE site at lightning speed on an advanced configuration, NGINX is probably the server for you. If you want to run MANY sites with easy configuration and flexibility, Apache is still your bread and butter.Īt the end of the day, both are a good fit for most sites. … then you probably want to stick with Apache.
Because of this, NGINX is often seen as the “faster” alternative to Apache, being able to handle a higher load of concurrent connections while using less resources. It features an event-driven design, which can make better use of today’s computer hardware than Apache’s process-driven design. NGINX (pronounced Engine ex) was released for production in 2004 and is rapidly becoming a popular alternative to the traditional Apache web server suite. This guide is not for everyone, but if you’re ready to grab the bull by the horns and deploy a web stack using NGINX, then you may use this guide as a first step to building common web stacks such as Node.js, LEMP, and popular web frameworks such as Django. It assumes a certain level of previous server administration knowledge, or at least a willingness to learn. This guide will help you with replacing Apache with NGINX on a new server. As a savvy web professional, you likely already know some of the advantages of the NGINX web server as opposed to the traditional Apache configuration.
So you’ve just gotten your new self-managed server and want to install and configure NGINX.