NGINX

NGINX is good for load balancing and in scenarios where u require a reverse proxy for security

When delivering a website and you require security and protection for your Kubernetes clusters or API gateways.

High SLA low latency environments
Light weight compute

i love to recommend this product to any of the web application or API's

Very suitable for web load balacing

Can be used as a reverse proxy

Reverse Proxy

So far for me it's been great for forwarding https and http traffic to different servers behind the firewall. I still use apache as the web service at the end, but nginx as a forward proxy for us has been great.

We do not find any simpler or faster to deploy web server/reverse proxy in Azure or AWS Marketplaces than with NGINX.

It's pretty much good for all the web applications.

It's well suited as I already mentioned. So basically one of the best hosting tools I use, so I would like to use that one feature also.

I'm not that familiar with those scenarios.

Nginx does well as a reverse proxy and not as well as a load balancer compared to other load balancer

Well served as a proxy reverse, we implemented in our environment to secure access by not exposing the app server directly to the Internet. As the product is really oriented, I don't see where it could be less oriented for. I think is well suited for load balancing the application access through proxy reverse, but this feature I haven't tested yet.

Well suited for web server hosting, load balancing, using reverse proxy to point to an alias. I don't think we can leverage it fully on windows

I use NGINX for routing application traffic to the appropriate endpoint.

NGINX is well suited for external traffic routing.

NGINX is the best product out there, and it's pretty much free.

NGINX is easy to install and use. The configuration is simpler. It is fast and especially great for static files. SSL configuration is also easier.

The best scenario for NGINX is when you need to create a front-end proxy that can handle several different domain names, certificates, and configurations. Each of these configurations can be built out in a single server pointing to multiple back-end servers and services. NGINX may be less suited if you have a very simple one server/one domain setup that doesn't need a lot of customization and configuration.

Ngnix is best suited as a public-facing proxy for everything that you might want to host. From WordPress to APIs, Ngnix does an extremely great job passing requests to those services, logging these requests in flexible ways, throttling requests when necessary, and even simplifying the downstream services by taking on some of the path extraction responsibilities (like extracting variables from paths and passing them in as headers).

It's not an application server, although they're working on it.

[NGINX] is very well suited for high performance. I have seen it used on servers with 1k current connections with no issues. Despite seeing it used in many environments I've never seen software developers use it over apache, express, IIS in local dev environments so it may be more difficult to setup. I've also seen it used to load balance again without issues.

NGINX is my go-to solution for anything regarding HTTP traffic. Whether that's a simple web server or an advanced implementation of ingress-Nginx for Kubernetes.

The only problems a user can expect is while implementation and it's hard sometimes and things don't go as expected every time, but once implemented the performance and scalability it provides is beyond one's imagination. It makes everything so easy after implementation and we use it for out git repositories branch wise deployment using docker and GitLab.