NGINX

Using NGINX for some Reverse Proxy services for security purposes. Helps to mask the IP address of our true IP Address. Looking to see what more we can do with NGINX like its load balancing function and web functions.

We use it mainly as an API Gateway Load Balancer

Use as a reverse proxy and web server.

Apache web server has replaced by NGINX server. could see potential benefits by using this product instead of apache. Infact its quite convenient to change the configuration sand easily scalable

Load balancing of the mobile trading application. The. Challenge is skill. To manage the appliance

Using as a reverse Proxy
Using as a cache
Using SSL Offloading

We use as a Reverse Proxy

We use the NGINX forward proxy manager to manage a few sites coming into the network. all websites with different domains.

I use NGINX when building POC labs in Azure and AWS to demonstrate IaaS solutions. Both as a simple test web server or as a reverse proxy, depending on the specifics in the POC.

We use it as the ATTP server and it is one of the very popular ATTP servers on the market. It's free and it has really good speed compared with the all-party ATTP server.

I use it for mostly host websites or anything that needs to be host. So we have our on-prem server where we host ourselves.

So we use it in our app development. We use NGINX servers for deploying our apps. We don't have any challenges so far. We are pretty much happy with whatever NGINX provides.

We use nginx as a reverse proxy for web traffic for security reasons. We have also used it as an http cache.

We used it to allow our internal applications to be accessed by the Internet, this allows the application to be securely accessed through public networks since we secure the https access through public certificated issued by our organization. It simplifies the management of apps published to the Internet.

We use NGINX as a reverse proxy to protect internal applications and to implement web APIs, which allows us to securely connect end users, apps and other systems with our back end systems. The NGINX servers are easily deployed in our DMZ, they run reliably and use very little resources. I definitely recommend NGINX.

Most of our applications are container based and load balanced. Having multiple servers in the backend is challenging and using an external load balancer makes you lose control of the mechanics. That is where NGINX comes into picture. We create config files on our EC2 instances and control how the load balancer functions via NGINX

I leverage the NGINX proxy to forward external client traffic thru our AWS infrastructure.

NGINX routes external traffic from external clients to our infrastructure application endpoints. It solves scalability and availability issues and allows us to get off legacy solutions.

NGINX is a gate to our application; it is a great open-source product, one of the best out there.

We use NGINX to host web servers. It is great for serving static files and if we need a proxy server to host microservices running on different ports.

We currently use NGINX for a high-powered highly configurable web server. The ability to protect and reduce the attack surface area of our primary webservers was our primary need. NGINX was chosen to meet internal demands for a highly flexible webserver that can have multiple nodes and redirect/proxy traffic to protected servers.

We use NGINX as our web-facing server, behind which we have a collection of services serving various parts of our application. NGINX helps us map a single API over a variety of services, and make our API endpoints consistent across the various services. Nginx also helps with uptime, by helping us switch between various instances of the services in near real-time.

Many [NGINX] servers are used across the organization to load balance and serve content before hitting our nodejs express rest api backends or our node react express frontends. It helps maintain uptime when we encounter strange deployment errors that can take out one of our servers. In my experience is has provided amazing throughput with very little configuration.

We currently use Nginx for our ingress layer into our Kubernetes cluster as well as for setting up simple reverse proxies.

NGINX is basically used as a server for web applications as implemented in our organization, NGINX helps us solve many problems like accelerated reverse proxying with caching and the best for static content loading. The other cool security feature that we take the most advantage of is that NGINX Limiting the number of simultaneous connections or requests coming from one address which protects our app from attacks against our infrastructure.