NGINX Plus Pros and Cons

Nginx is extremely efficient in terms of the connection rate to the CPU cycles ratio, and in terms of the bandwidth to CPU cycles.

Application Gateway with application-level firewall tool and load distributor and balancer (also serves for A/B testing).

Valuable features include authentication, caching, reverse proxy routing, and load balancing.

The best solution, by far, for web traffic control for things in production and just around the house.

Its most valuable features are load balancing and application delivery. This is the most efficient application for these features because of stability and its efficiency.

The robust software architecture allows for it to be scalable and very stable.

​The flexibility of its modules allow it to be scalable.​

​Zero Downtime has always been a strength in recommending infrastructure web services. NGINX allows me to execute such infrastructure with less complications and the ability to switch from server to server easily.​

When I worked in a security research center, we tested NGINX to support DoS and DDoS attacks, and its results were great.

NGINX works much better than HAProxy in our current hardware and architecture for HTTP/HTTPS load balancing. ​​

Our most challenging part was to run an older PHP website reverse-proxied through NGINX. That was not fun.

The biggest room for improvement would be to allow NGINX Core machines to cluster for memory zones in some way with a plug and play module. ​

They should do in the open source version of what they did to Advanced HTTP, TCP, and UDP load balancing.

Make modules easier to enable or disable. The beauty and ugly side of the NGINX modules is you have to know how to compile the module. For beginners or non-very technical aspirant(s) going for NGINX, they have to learn how to compile the modules.​

I would like it to have a more user-friendly graphical interface.

If NGINX brings some features for health check in the open source version, it would be better. ​