NGINX is an excellent tool for load balancing and hosting backend servers
March 12, 2020

NGINX is an excellent tool for load balancing and hosting backend servers

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source

Software Version

NGINX Open Source

Overall Satisfaction with NGINX

WE use NGINX as a load balancing solution across our department. It provides a simple and easy to manage system for proxying and load balancing requests across an array of worker machines in a reasonable manner. It is low impact, high throughput, and low risk. As a major vendor, it has optional paid support.
  • Load balancing
  • High concurrency
  • High uptime
  • Handling of large numbers of certificates.
  • Higher response time.
  • Lower cost
  • Lower downtime
HA proxy is designed explicitly for proxying requests. It works well for this purpose, handling extremely high volumes with little issue. However, it lacks some of the features NGINX provides for running application servers. For our purposes, NGINX provided us with a high amount of flexibility while still being the more commonly used product which lowered the barrier to entry.
I'm explicitly rating the open-source version of NGINX here. The open-source version has good documentation and useful examples. As one of the most web servers in the world, there is a wide range of tutorials and examples to learn from. This does have the drawback of potentially using older documentation, but NGINX has excellent default behavior, and the official documentation is easy to use. Their paid support seems excellent as well, though we haven't taken advantage of it yet.

Do you think NGINX delivers good value for the price?


Are you happy with NGINX's feature set?


Did NGINX live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of NGINX go as expected?


Would you buy NGINX again?


NGINX is an excellent load balancer and can run a variety of WSGI applications. It is very useful in situations where you want to be able to maintain high availability while updating the backend servers, due to its ability to reload configurations without downtime. It is less useful for running a backend service itself, though it still performs that task adequately.