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.

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

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

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.

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

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.

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 have used NGINX in several different ways. We've used it as a load balancer, a proxy server, and a web server. Its ability to do one or all three of these jobs is what makes it so useful.

I use NGINX for two main purposes. The first and foremost is to serve as a reverse proxy to rails applications running on their own servers. This includes making use of gzipping and SSL/TLS encryption. Additionally, it is used to serve compiled react applications as static sites, with the other instance still serving as a reverse proxy to these.

Nginx is widely used in the whole organization for different applications as a front end hitting web server. It's used generally to benefit the caching mechanism and load the balance of the clustered applications and also used widely to maintain an active environment in case of any node failure or application server failure.

Nginx is present at different levels across my projects. Sometimes is just a Web Server, others a Load Balancer or an API proxy with SSL/TLS management, it's just great that's so lightweight that you can deploy as many instances as you want, for different purposes and create a services mesh inside your organization's network.

We use Nginx as a load balancer and as a reverse proxy for all of our web services. We use it to serve NodeJs applications, REST APIs and Angular front.

Nginx is an excellent choice for any size company, be it a startup or mid to large scale. iI delivers a well-supported server architecture without much fuss involved. I loved the customer support I received whenever I sought help for several different client projects. Nginx is a great choice for use with AWS EC2 instances as well as I've personally used and configured it without any bottleneck. So I can say that it is a good choice for AWS and similar cloud hosting solutions.

Ever since discovering Nginx as an alternative to Apache, it has been my web server of choice for a variety of purposes, whether it be creating a versatile development server accommodating a variety of platforms across many different sites, or setting up a high-speed scalable server with integration with a popular content management system for a client. The powerful yet flexible configuration options of Nginx makes it straightforward to configure a server for a multitude of different tasks, and a clear choice for almost any situation.

We use Nginx to serve static content for a few of our applications. Nginx is very effective for us because it's free, scales very well, and can handle millions of requests a second. It has made several of our websites noticeably faster. In addition, its ability to act as a Proxy/Reverse Proxy has been instrumental in fulfilling our specific web hosting needs.

We use Nginx widely as our primary way of proxying and SSL termination. Specifically, our highly-available architecture used for both a bidding environment and serving ads are designed with Nginx. We have had success building out some applications with deeper Nginx integration as well, our own home-built CDN.

We use Nginx as load balancing for our complex web applications and proxying requests to different applications across the company. It has a small footprint and memory usage, so it's the best choice solution for us.

We use Nginx Plus Professional as a load balancer and as a reverse proxy with its ModSecurity component - WAF (Web Application Firewall). Nginx supports all the web traffic of the whole organization and some of our clients.

We use Nginx as the primary reverse proxy for all of our web services. We manage several dozen web applications, for many different clients, and Nginx allows us to quickly route requests to the correct service. Since we use Kubernetes to manage services, it is fast and simple for us to add new routes to our Nginx service. Nginx also manages our SSL, allowing us to deliver content securely.

Nginx is powering the serving of web content across our entire organization. We used to host over a hundred web servers with Rackspace Cloud all with nginx sitting in front of backend server processes. Now, we host the majority of our sites on Pantheon, who also utilize nginx in their app server layer. We also host a number of custom servers on AWS EC2 which serve web content over nginx. It allows us to squeeze more performance from our web servers much more easily than using Apache.

I have used Nginx for years to serve Ruby on Rails applications for a number of clients and with various integrations including Passenger and, more recently, Unicorn. I have found Nginx to be a wonderful choice for both standalone server and layer in front of Unicorn. Nginx excels at serving static files, load-balancing, security (preventing certain exploit attempts) and simply acting as a front end for full-featured application server back-ends.

Nginx is used as the main web server and load balancer in front of our Rails apps. We use Nginx + Passenger together as part of our stack for production deployments of our Rails apps.

We currently have 5 different deployments of Nginx, and everyone in the company that deploys production apps uses them.

The main business problem addressed by Nginx was definitely speed and load balancing. Before using Nginx + Passenger, we had Apache servers in front of Mongrel for our rails apps, and they not only were slow and memory intensive, the only load balancing strategy available with that setup was round-robin allocation of incoming web requests to different app servers. With Nginx, it acts as a load balancing proxy as well and keeps track of which app servers are free to receive new requests. This resolves bottlenecks in our server's performance.