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.
External reviews
38 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Enables public access and secure configurations through reverse proxy
What is our primary use case?
What is most valuable?
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.
What needs improvement?
One area of improvement could be that NGINX could provide a means to generate self-signed SSL certificates. This would eliminate the need to use third-party software such as SaaS Boost for generating these certificates.
For how long have I used the solution?
I have been working with NGINX for seven months.
What do I think about the stability of the solution?
NGINX is very stable. In my use case, I require ninety-nine point nine percent uptime, and NGINX has been pivotal in helping me achieve this along with our other DNS services. I have not encountered any stability issues.
What do I think about the scalability of the solution?
While some people use NGINX for web servers, my current use case focuses on networking and tunneling, which does not necessitate much scaling. However, by adding more resources to our system, I can maintain and ensure everything runs smoothly.
Which solution did I use previously and why did I switch?
Prior to NGINX, I didn't use any other similar solutions.
How was the initial setup?
The initial setup of NGINX was straightforward and very easy. It was completed in about one hour.
What about the implementation team?
The entire deployment process required only one person.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
My use case involves using the free and open-source version of NGINX, making it cost-effective as I haven't incurred any costs.
Which other solutions did I evaluate?
I did not evaluate other options because NGINX is popular in the tech world and was an easy choice for me.
What other advice do I have?
NGINX is a great product for anyone interested in reverse proxy. It is a reliable solution and has proven effective in my use case. I would recommend it to anyone considering similar needs.
The overall product rating is ten out of ten.
showing 1 - 1