Nginx Reviews

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.

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 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.

Nginx is the DEFAULT web server for our organization and projects that we work on. I don't think Nginx as a simple web server but a micro service that is part of the whole application. As a DevOps [solution], it has made us more independent rather than relying on developers for every small requirement. Now we can just write a few lines of code in Lua or js and get our solution ready as a hotfix rather than going back and forth and trying to make developers understand what is needed. In some cases, our few lines of code prove to be a better solution than an application :)

I would suggest having one layer of Nginx on top of your JAVA or Node application. If you never use it as we do it will still handle the web connections better.

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.

Nginx is the main competitor to Apache. It provides stable service. I have been using Nginx for the last four years and it has never gone down even once, which is critical for a web server. I also like the flexibility and compatibility Nginx has with other components in web development. I switched from LAMP to LEMP, which works great as an environment for WordPress and other PHP software. Overall, it is a great choice for a web server.

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 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.

We used it to deploy web applications built using popular JavaScript frameworks such as Angular and React.

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 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.

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.

Nginx is my default go-to web server for all Linux web servers (LEMP Stacks) that I currently deploy. I use NginX primarily as one of several pieces of a custom-designed web-server stack in conjunction with Ubuntu or CentOS, Percona XtraDB, and HHVM with PHP7-FPM failover, which is used to power PHP based websites (such as WordPress) which I deploy on entry-level compute packages provided by industry standard cloud services (AWS, Google, BlueMix, Digital Ocean) for our web-design clients. My primary goal with these servers is to provide our clients with their own managed, in-house hosting solution with more power than a standard hosting company can provide, but at a similar recurring cost bracket. Nginx was my choice, as it was designed specifically to win the C10k challenge, which was a challenge to create a web server capable of handling 10,000 simultaneous connections on a single server (which was successful). The biggest challenge I face is designing a stack that can handle a potentially heavy connection load while deployed on low-spec, shared-resource, sub-$20 virtual servers, while avoiding the expensive, constant need for computing resource increases. These challenges require a web server than can handle 1 or 1,000 connections on the initial specs, without an increase in resources, which Nginx was able to accomplish beyond my expectations, allowing me to provide similar and sometimes equal performance on virtual servers as that of higher-cost, WordPress specific hosts, such as WP Engine.

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.

We've used Nginx in several capacities.
- dynamic routing of ingress traffic to Docker containers
- load balancing web applications
- proxying requests to different applications

Nginx is a http server software used to serve up websites across the web, similar to Apache httpd. The main difference being that Nginx offers multi-threaded support to serve up websites faster and more efficiently. I implement and use it as often as possible for my websites I build in order to provide the speed and efficiency that is required. It is easy to use one config file to serve up both the http and https versions of the site.