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.

NGINX is extremely fast when used as a web server. We used it for many years to serve up static content such as images, css, html, and javascript. The proxy features are also great for routing traffic through it when needed.

NGINX is well suited for a forward-facing web server. While as a reverse proxy, I had better results with APACHE, I try and use NGINX for anything that I need to run a reliable and secure web server on.

If you want to serve a static website, implement a reverse proxy server to in-house applications running on their own servers, enable SSL/TLS encryption for your sites, load balance between application instances, or simply cut down the size of your server's responses by gzipping them, then Nginx is for you. If you feel that you need a GUI to do any of these things, then potentially look elsewhere.

Nginx is best to use as front end proxy for any application server. Nginx's cache mechanism is one of the best as compared to other web servers. Nginx is really a light weight webserver and it provides more flexibility in case of load balancing in clustered application. Configuration of Nginx is very easy as compared to other web servers. Nginx uses fewer resources of hosted server.

Nginx is perfectly suited for anyone with Linux in their environment and who needs a powerful web or app server. It might not work as well for an all Windows shop.

When deploying API services, we need to take care of many aspects of the network where they work. Infrastructure is also a factor when limited, so you also need to limit and manage it according to its use. Nginx is great to construct these network nodes (HTTP, API Proxy) that connects everything and can add extra capabilities like security (ModSecurity, SSL/TLS) and availability (Load Balancer, Rate Limit).

If you want to start learning web application architecture, Nginx is a great start. It is one of the easiest web servers to deploy and use. The configuration file is easy to use and understand. You will not feel overwhelmed learning it. If your company needs a lightweight web server or even simply just a static host, you can choose Nginx. It is super reliable and easy to use. It is also pretty much carefree. Just deploy it and you are done. When thinking about choosing servers, the best start point is the needs of your company. Nginx fits in the same category as other flexible, consistent, lightweight servers.

Nginx is a very good web server and proxy. To serve NodeJs applications, Nginx + pm2 is very efficient. Coupled with Passenger, it allows MEAN Stacks applications to be deployed very easily.

It is well suited for creating your custom CDN without much payload on the server and a proxy solution is also very effective using Nginx. Great for websites having high traffic demands but could be a bit heavy for smaller projects where traffic is low. Overall effectiveness of the Nginx solution is great when compared to competitive solutions provided by Apache Server.