NGINX Plus Reviews

I am using the NGINX web server as my web server, especially to run PHP applications and Python. The main reason that I am using NGINX in these environments is micro caching. NGINX is a lightweight web server. 

Writing rules and configurations in NGINX can be more handy than Apache. Another usage is as a load balancer. NGINX works much better than HAProxy in our current hardware and architecture for HTTP/HTTPS load balancing. 

Because of our usage:

• Micro cache
• Rate limit
• Upstream (load balancing).

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

First, I used NGINX as a reverse proxy web server for Apache.

I love NGINX, which is why I am rating it as a 10 out of 10.

NGINX has been primarily used as a web server, which is also used as a load balancer. The robust software architecture allows for it to be scalable and very stable.

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.

NGINX's multi-thread compatibility has been the integral part of it being a robust enterprise solution. 

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.

It is very stable.

The flexibility of its modules allow it to be scalable. You just have to know how to integrate them with various enterprise scenarios.

I have been using NGINX for five years. I have implemented various NGINX solutions to different client requirements.

I have no problems with it. Its stability is what makes it very much recommended as a solution for any enterprise to utilize.

We are using NGINX to provide a reverse proxy in an environment of web services.

The product is free, reliable, and safe. 

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

It is reliable.

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

No issues yet.

No issues yet.

We used Microsoft ForeFront and changed because it was not stable during DDoS attacks.

It was a simple setup.

NGINX is a free tool in Brazil. There are some companies which do support it. The price is the cost to contract support with a specialized company, usually during consulting hours.

No.

I have been using it for eight years.

Simplicity, stability, and modularity. Because, if you are familiar with Apache, you will know why my first reason is simplicity. Nginx is simple to configure, very stable in a highly utilized environment and very modular, allowing DevOps to create it's own modules for interactive use with Nginx.

It lowered overall bugs and increased system stability. Also, it allowed our system to serve many more clients than the old system did.

Only improvement needed that I would point to is scalability. With it, I mean clusterized organisation on a low level. At the moment, the best alternative is RHEL HA.

Around four to five years.

No.

Yes. As I explained in areas for improvement.

I have no experience with the Nginx technical team.

Yes, Apache. It was terribly complex for usage and unstable in a production environment.

Complex. It needed a complete product rework.

I have no advice. Nginx is free. I don't have experience with the Plus version.

No.

Use community knowledge. Nginx is widely used worldwide and there are many experts on the web that will help you out. Also, read the documentation. Its documentation is excellent.