NGINX Plus Reviews

I am a reseller. A lot of customers use this solution on cloud and on-premises. Typically, people use NGINX to build their own CDN solutions, so it often goes into CDN deployments. Most apps have NGINX OSS as the underlying base, whether they're cloud apps or on-premises apps. NGINX is the free version of NGINX Plus.

F5 is now creating buzz in the market because if you migrate to NGINX Plus, you'll get a 30 minute response time from F5 or the NGINX team if you have any challenges with the solution, so that's an advantage. 

NGINX Plus can give you multiple features from a load balancing perspective. The standard NGINX OSS doesn't have that.

There are about 400 million websites that run NGINX OSS. Since NGINX was an open source company until F5 acquired it in 2019, NGINX doesn't have a lot of paid products. In the last year and a half, the F5 and NGINX teams have started doing the sales pitch for people to upgrade to the paid version, like Red Hat, which has an open source version and a paid version. We're seeing good uptake, but I don't think they have been able to cover more than 10% of the user base.

For most of the companies I have interacted with, 90% of them are using NGINX because it's a favorite open source solution. People are now using NGINX Plus because F5 just started selling it in the last year and a half. Out of the 90% who are using it, there are about 10-15% who are using the paid version.

It definitely improves functioning. The virtual load balancing applications from F5, Radware, or any other provider are typically very heavy apps and demand at least 8 to 16 CPU of processing power. Typically, each of the install files are 3GB or 4GB, compared to NGINX Plus, which is hardly 3 or 4MB. It installs very quickly and is very easy to manage when you're doing orchestration or automation.

NGINX is very DevOps friendly compared to other load balancing modules from F5, Radware, or Citrix.

I use NGINX to port our local server to a public server where people can access the URL. The main use case is for reverse proxy to support our local server, making it publicly accessible through our DNS system.

The primary valuable feature of NGINX for me is its ability to provide a reverse proxy. I have found that this feature supports our local server, and I am able to connect through our DNS system, making it accessible publicly. 

Additionally, the integration with SSL certificates and the configuration capabilities make it a valuable solution for my use case. Without NGINX, users would not be able to access our application, which means there is positive ROI from using NGINX as it is crucial for the functioning of my organization.

We use the solution for application transactions. It is used for our corporate business and customer-facing applications.

The solution enables good messaging between two data centers. The product is resilient. It provides a single API. It is a pretty solid solution.

I primarily use this solution for API management, WebSocket, and WebServer.

I use NGINX, which is integrated with our engineering server, SparkFi. We are using NGINX Plus, which functions as a responsible application, serving as a reverse proxy and a small web server. For API management, the WebSocket, and the WebServer, NGINX provides a cost advantage, value addition, and effective support.

We use NGINX as a reverse proxy. For example, if you access www.google.com, NGINX accepts the external traffic and forwards it to the internal application servers.

NGINX can also be used for load balancing, which makes it better than Apache in a lot of cases. Additionally, it functions as both a reverse proxy and a web server, offering a lot of flexibility.

Moreover, it performs very well. That's one of the primary reasons we use NGINX.

I find NGINX Plus incredibly versatile. It is my go-to for serving web content efficiently, balancing loads across servers, and securely managing traffic as a reverse proxy. Plus, it is fantastic for streaming ports like SMTP and handling non-SAP protocol traffic.

Using NGINX Plus for web traffic distribution is fantastic. It offers performance similar to physical load balancers but with added flexibility. However, I have faced challenges with DNS configurations. Sometimes, updates to domain name IPs take time to reflect, causing delays or caching issues.

We are using servers as web servers, and I redirect them to NGINX.

When you use NGINX, you have more options and power. You don't need to use anything else. I have web servers that integrate with other web servers you need to use, for example, Apache, IIS, or anything else.

We have two to three use cases for the solution. The first use case is for our organization’s Base Server that is hosting the applications. The second is the load balancing and reverse proxy. The third use case is NGINX App Protect which we are using right now.

I find the solution’s community support and documentation most valuable. Compared to HAProxy, have found a lot of documentation and community support on Quora. If you would be asking me as a developer whether to choose this product, I would recommend this since it has good community support, documentation, and signature updates. The configuration of HAProxy is also very tedious. However, NGINX’s configuration is very simple.