At the start of this millennium a unique web server problem emerged: the C10K problem. In other words, how can a web server deal with ten thousand connections that are made to it concurrently? NGINX was the response to this question: developed in 2002, the first release of NGINX that was made public occurred in 2004.
Concurrency is a big issue and that’s why NGINX is second in line after Apache in terms of the number of web servers using it, with a little more than 30% of the websites on the internet making use of NGINX to serve web pages.
The architecture of NGINX is different from Apache, which is what makes it possible for NGINX to handle so many concurrent sessions: NGINX uses an event-driven architecture that is asynchronous to perform its magic. Because of the fact that NGINX can handle concurrent sessions using relatively little in resources it has become very popular with website administrators who appreciate the fact that NGINX scales easily.
NGINX is very flexible: you can deploy NGINX as a web server, but also as a load-balancer and NGINX can also operate as a proxy server. NGINX, just like Apache, has a community site that you can refer to over here
with