What is our primary use case?
We build all our websites (of which we have multiple, from production sites to development environments), through webpack, so we use NGINX to quickly host them, while easily binding to the relevant (sub)domains. Our entire service stack runs on Linux. Our most challenging part was to run an older PHP website reverse-proxied through NGINX. That was not fun.
How has it helped my organization?
NGINX isn’t itself a productivity tool, but rather a cog in the engine of a solid service stack. In a way, it's the same as adding RAM to a PC. While you don’t necessarily feel the new improvement, you’ll definitely know when it’s gone.
What is most valuable?
Our primary use for NGINX is as a Web server, so that’s where we derive the most value. Recently, we’ve needed to deploy sites over a number of servers to balance the load, which was not only painless but also super valuable.
What needs improvement?
We used the standard tried-and-tested features of NGINX. Everything is done through the CLI over a secure connection and there have not been any issues or additions to our wish list.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
NGINX has an amazing developer base which ensures amazing stability.
What do I think about the scalability of the solution?
We’re only just getting into the scalability side of things, so no issues yet.
How are customer service and technical support?
Never needed technical support (which speaks for itself).
Which solution did I use previously and why did I switch?
We tried to use some "golden bullet" solutions but we never needed most of their features (like a built-in database environment). NGINX is a direct way to satisfy a specific need.
How was the initial setup?
This was installed on an Ubuntu system. The setup and deployment is well documented which lead to creating an easy hosting environment.
Which other solutions did I evaluate?
The idea of using other lightweight solutions, or a native Ubuntu Web server, was completely overshadowed by NGINX.
What other advice do I have?
Support the developers and the product, they’ve worked really hard to give you something you’ll always be satisfied with. First, set up a free environment and see your limitations, and then pay for what you need.
Always do a setup and test on a small (possibly in-house) server. Work out all your kinks and processes, then deploy it to a production environment. Having something like docker helps immensely.
I rate NGINX a 10 out of 10. Really, the only other options are native solutions that are either super convoluted or don’t have the needed features.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Apr 30 2018