So it's primarily for testing purposes.

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.

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.

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.

It is stable. We have faced connectivity issues only once or twice. Otherwise, it has been working fine.

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.

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.

The initial setup was not complex. It was easy. It took us one or two days to set it up.

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.

We are currently using the free version of NGINX. No costs have been incurred yet.

We had other solutions like BIG-IP.

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.

I use the solution as a reverse proxy. 

The product is lightweight and fast. 

The solution needs to be easier to setup and deploy. 

I have been using the product for two to three years. 

I would rate the product stability a ten out of ten.

I would rate the product scalability an eight out of ten. 

The tool helps us to improve our website speed. 

I use the solution's community edition which is free of cost. 

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. 

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.

It's lightweight software that can handle heavy loads efficiently.

There is room for improvement in the pricing model. 

I have been using this solution for three years. 

The customer service and support is fine. 

The initial setup is straightforward. It took about a week to deploy the solution.

There was an ROI. It's a very useful solution.

The licensing cost is yearly, and it can be quite expensive.

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.