Proxy and load balance are the reasons why I use NGINX Plus. I use NGINX Plus to help me with a delivery app on the cloud for one of my company's customers.
NGINX Plus Standard - Amazon Linux 2 (LTS) ARM Graviton
NGINX, Inc. | v1.17Linux/Unix, Amazon Linux 2 - 64-bit Amazon Machine Image (AMI)
External reviews
39 reviews
from
and
External reviews are not included in the AWS star rating for the product.
A simple-to-configure tool offering functionalities for load balancing that needs to improve its GUI
What is our primary use case?
What is most valuable?
The most valuable feature of the solution is that it is simple to configure.
What needs improvement?
The solution's GUI is an area with certain shortcomings that need improvement. The price of the solution is also an area that needs improvement.
In the future, I would like to see the solution to have better capabilities in terms of basic checks and reporting.
For how long have I used the solution?
I have been using NGINX Plus for two years. I don't remember the version of the solution.
What do I think about the stability of the solution?
Stability-wise, I rate the solution an eight out of ten.
What do I think about the scalability of the solution?
Scalability-wise, I rate the solution a seven to eight out of ten.
How are customer service and support?
I rate the technical support a nine out of ten.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup of NGINX Plus is very simple to deploy since it is done on a cloud.
The solution is deployed on the cloud.
What's my experience with pricing, setup cost, and licensing?
The cost of NGINX Plus is high. NGINX Plus is an open-source solution with limited additional features. When you try to get additional features in the solution, then you need to pay an extra amount to NGINX Plus.
What other advice do I have?
NGINX Plus offers limited functionalities when it comes to load balancing.
I rate the overall solution a six out of ten.
Light-weight tool and route traffic geographically and act as a proxy for managing traffic flow in complex networks
What is our primary use case?
So it's primarily for testing purposes.
What is most valuable?
With NGINX, I appreciate its ability to route traffic geographically. It acts as a proxy in the middle, which helps us manage traffic flow in complex networks.
It takes the load off the actual mission-critical applications and transfers the traffic to the main applications with less burden. It's a very useful tool to have in your profile.
What needs improvement?
One thing I would love to see is a feature similar to what Elastic offers. When Elastic receives data from any server endpoint, it allows you to either save it into an index or print it on the terminal. While debugging and testing the load balancer, it would be helpful to have the option to print data on the screen. This way, we can verify that the load balancer is receiving the correct data and displaying it on the screen.
If this feature exists in NGINX, it would be great to have a flag or switch that enables displaying data on the terminal for verification of network traffic.
For how long have I used the solution?
NGINX is a very lightweight tool. We deployed NGINX on a simple, minimal specification machine. We used the configuration provided by Wazuh on its documentation website. The only thing we had to do was provide the IPs of our own machines. Everything else remained the same. After that, we were able to load balance the traffic from all the endpoints.
This was our first experience with NGINX as a team. We used it specifically for load balancing across all those endpoints. Apart from that, we don't work with NGINX.
We have been validating Wazuh for one year, and we have been using NGINX for almost two months. During the testing phase, we had to ensure that NGINX met all the requirements for building a redundant custom solution, including multiple nodes and a load balancer. However, during testing, we didn't require any additional load balancing or extra functionalities.
What do I think about the stability of the solution?
It is stable. We have faced connectivity issues only once or twice. Otherwise, it has been working fine.
What do I think about the scalability of the solution?
We haven't encountered a use case that required us to scale NGINX. We have two NGINX instances in Wazuh cluster, which helps distribute the load across different servers. So, as of now, no scaling requirement for NGINX.
Currently, I am the only person working with NGINX.
How are customer service and support?
We inquired about the procedure for official support from Wazyh itself. They provided us with a price quote based on the number of endpoints we would be covering. However, we haven't purchased that. We are currently using the open community and Slack for support.
How was the initial setup?
The initial setup was not complex. It was easy. It took us one or two days to set it up.
What about the implementation team?
The deployment was simple. We used the Linux installation command, and then we followed the configurations provided by Wazuh. We copied and pasted the configurations into the specified directories. We replaced the tags with our own IPs, and we were good to go and start using NGINX.
Currently, only one engineer, which is me, has been managing Wazuh for the past year. NGINX does require maintenance. Maintenance is usually not required unless there are rare cases of design changes or version upgrades. We rarely need to schedule a maintenance window for Wazuh, maybe once or twice every six to four months.
What's my experience with pricing, setup cost, and licensing?
We are currently using the free version of NGINX. No costs have been incurred yet.
Which other solutions did I evaluate?
We had other solutions like BIG-IP.
What other advice do I have?
I would recommend watching videos, YouTube tutorials, and concise documentation related to the specific use case. For example, in our case, we focused on load balancing, so we referred to the version documentation on how to configure NGINX as a load balancer. Also, make use of the official NGINX documentation.
I would rate it around nine out of ten. It hasn't disappointed us, and for our use case of load balancing, it performs exceptionally well. So, a solid nine every time.
Which deployment model are you using for this solution?
On-premises
A lightweight and fast reverse proxy solution that is easy to maintain
What is our primary use case?
I use the solution as a reverse proxy.
What is most valuable?
The product is lightweight and fast.
What needs improvement?
The solution needs to be easier to setup and deploy.
For how long have I used the solution?
I have been using the product for two to three years.
What do I think about the stability of the solution?
I would rate the product stability a ten out of ten.
What do I think about the scalability of the solution?
I would rate the product scalability an eight out of ten.
What was our ROI?
The tool helps us to improve our website speed.
What's my experience with pricing, setup cost, and licensing?
I use the solution's community edition which is free of cost.
What other advice do I have?
I would rate the solution a nine out of ten. You need to be careful with the product's configurations. It is easy to maintain.
Lightweight software and easy to setup
What is our primary use case?
NGINX Plus is a part of F5 and can be useful for customers with containers and terminals. Moreover, it's useful for businesses that need application delivery control and enterprise load balancing.
What is most valuable?
It's lightweight software that can handle heavy loads efficiently.
What needs improvement?
There is room for improvement in the pricing model.
For how long have I used the solution?
I have been using this solution for three years.
How are customer service and support?
The customer service and support is fine.
How was the initial setup?
The initial setup is straightforward. It took about a week to deploy the solution.
What was our ROI?
There was an ROI. It's a very useful solution.
What's my experience with pricing, setup cost, and licensing?
The licensing cost is yearly, and it can be quite expensive.
What other advice do I have?
Overall, I would rate the solution a ten out of ten.
If you're using a container environment, I would highly recommend it. It's usually a good fit in about 58% of cases.
Which deployment model are you using for this solution?
On-premises
F5 NGINX Plus - Modern Application Platform!
What do you like best about the product?
F5 NGINX Plus is one of the best API monitoring and security enhancing platforms that simplifies the process of modernizing legacy, monolithic applications as well as delivering agile, micro-services applications to enterprises undergoing digital transformation. With API Gateway and load balancer features, this is a robust cloud-native load balancer ingress solution that is super resilient, scalable, and dynamic.
What do you dislike about the product?
There's not a lot to dislike about NGINX except the platform latency, slow support service, and a bit difficult to understand UI. Apart from this, the tool is great and really profitable for businesses seeking quick API deployments!
What problems is the product solving and how is that benefiting you?
The platform introduced many benefits for our business such as reduced complexity, flexibility in API management, easy-to-set up and better integration, intuitive dashboard, and real-time monitoring.
complex but very useful
What do you like best about the product?
NGINX F5 is very useful for load balancing.
What do you dislike about the product?
Complex for early learners and installation might me tricky.
What problems is the product solving and how is that benefiting you?
Load balancing for my product.
simple and easy to use
What do you like best about the product?
fast webserver for the load balancer and easy to implement.
What do you dislike about the product?
First time it is look like hard but it is easy after that.
What problems is the product solving and how is that benefiting you?
load balancing
NGINX is flexible with configuration and handles a lot of traffic
What do you like best about the product?
Easy to configure with no restart. Scale based on traffic and rules.
What do you dislike about the product?
Better GUI for monitoring and missing configuration wizard
What problems is the product solving and how is that benefiting you?
Handles load and use as reverse proxy
Nginx webserver cum loadbalancer
What do you like best about the product?
The best thing is you can deploy ngix service very easily on any platform. Since docker image is also available for nginx, its much easier when you are looking micro service application load balancing.
What do you dislike about the product?
The content is not presice I guess. The video content is also very limited if you for looking for any specific thing about Nginx plus. More video content and reliable doc would be great.
What problems is the product solving and how is that benefiting you?
For me earlier platform dependency was issue when deploying a Nginx server on different platform. Nw Nginx plus solve this issue by creating the Nginx plus docker image.
Good performance
What do you like best about the product?
Platform Scale, Deployment Flexibility and ADC functionality are excellent.
What do you dislike about the product?
The major drawback is that everything needs a license.
What problems is the product solving and how is that benefiting you?
The proxy setup and load balancing features help a lot to make the production environment more stable.
showing 11 - 20