nginx vs. Unicorn vs. Kore

I don't have a strong preference between using Apache and nginx, but I find that the config files for nginx to be much more manageable.

The original API performed a synchronous Nginx reload after provisioning a zone, which often took up to 30 seconds or longer. While important, this step shouldn’t block the response to the user (or API) that a new zone has been created, or block subsequent requests to adjust the zone. With the new API, an independent worker reloads Nginx configurations based on zone modifications.It’s like ordering a product online: don’t pause the purchase process until the product’s been shipped. Say the order has been created, and you can still cancel or modify shipping information. Meanwhile, the remaining steps are being handled behind the scenes. In our case, the zone provision happens instantly, and you can see the result in your control panel or API. Behind the scenes, the zone will be serving traffic within a minute.

It's not Apache.

SSL and routing requests.

For serving static/cached files

Backend web server for Fastly. Serves font files and PHP.

This functions as our load balancer and traffic cop directing API and incoming requests to the correct component.

As a reverse proxy and static content server.

Used to be Apache, but configs, robustness and performance of nginx - obviously made sense.

Nginx is the webserver we use in front of the Unicorn application servers. We have multiple Unicorn workers for every application (depending on their performance requirements), and Nginx basically functions as a load balancer.

Our super-fast webserver.

Static web server

If you have a static site with us, it is served by nginx + palu-gateway.

Great for load balancing

The server is comprised of Varnish, Nginx & Apache it is SPDY and an excellent product.

어플리케이션, 백엔드 서버는 모두 nginx 를 통해 reverse proxying 되어 서비스 됩니다. nginx 는 빠르고, 안정적이고, 매우 간편합니다.

Our webserver of choice. Fast, accurate, powerful, rock solid.

As web server to talk to PHP-FPM

1. Performant
2. Simple/easy-to-configure
3. Scalable
4. Free

Not many web servers can offer all four, but nginx can.

A solid front end server to the Django environment.

Front-end proxy and load balancer

Nginx is used to serve the site from within Docker via Passenger, as well as for error page and www to non-www HTTP redirects.

We are using NXING to server and cache static files and as a load balancer in front of our Apache webservers.

We switched from Apache to nginx for a speed boost, since we only need a light web server.

fast

We use nginx to serve all of our static files, and to load balance our multiple backends. Our nginx frontend servers are themselves load-balanced using a Linode NodeBalancer.

Needed for our micro services architecture and best to scale the whole system into docker containers in teh cloud.

Serving static files

Load balancer and proxy server

We use NGINX both as reverse HTTP proxy and also as a SMTP proxy, to handle incoming email.

We previously handled incoming email with Mandrill, and then later with AWS SES. Handling incoming email yourself is not that much more difficult and saves quite a bit on operational costs.

Allows us to run an Apache Webserver and a Node.js websocket server on port 80 on a single host

Webserver for static data.

nginx is frequently used in our web applications as a proxy that also servces a few static files or that adds some HTTP response headers, e. g. for client-side caching.

Webserver

Nginx makes Big Lou Insurance fast and snappy!

Our core web server stack

Nginx serves client https requests and acts as an sslproxy to the gunicorn application server. Rewrites request headers.

Nginx is a caching proxy that provides basic load balancing for our API and serves our rich client applications to end-user browsers.

I use nginx as a reverse proxy.

Serving any and all static content to the client.

Our webserver

NGINX is quite possibly our favorite tool on the serverside, because of how easy it makes load-balancing. You just throw it in, tweak the config and boom, you're up and running in minutes.

Fast!

I use to prove web page service.

Reverse proxy supporting HSTS and Elliptic-Curve Diffie-Hellman key exchange for perfect forward secrecy - AWS ELB doesn't support the range of HTTPS optionsthat nginx does.

Node proxy

Web server and image CDN edge server.

Hosting provider stack

As an HTTP and websocket gateway

URL routing.

Nginx serves as the loadbalancer, router and SSL terminator of cloudcraft.co. As one of our app server nodes is spun up, an Ansible orchestration script adds the new node dynamically to the nginx loadbalancer config which is then reloaded for a zero downtime seamless rolling deployment. By putting nginx in front or whatever web and API servers you might have, you gain a ton of flexibility. While previously I've cobbled together HAProxy and Stun as a poor man's loadbalancer, nginx just does a much better job and is far simpler in the long run.

Sit's in front of our web apps

Used to load balance all services as well as cache static content

NGINX works with PHP to serve the content for our pages, its event driven system is both lightweight and responsive.

Static file server and reverse proxy for our API.

Runs our HTTP server.

Reverse proxy + static files serving

HTTP Server and reverse proxy

Nginx serves as a proxy for dynamic data and delivers static content.

Nginx, как обычно, проксирует динамические запросы бэкенду и отдает статический контент.

Proxying to Passenger.

Static file serving, TLS terminator & HTTP upgrader for secure WebSocket.

nginx is the web server running on the host.

Simple, no hassle, small dependencies and utilized to serve different stuffs easily (fcgi, reverse proxy to golang, nodejs and rails)

Very fast and configurable web server

SendBird API server

Nginx is used as an integration point of both static resources and API.

All incoming requests pass through our high redundancy load balanced nginx instances, no matter if it's static resources for the websites, API calls via uwsgi or TCP stream-based services.

For Rails

As a reverse proxy for thin instances and some hook responders for automated deployment

Good to have. 10K+ concurrent requests, load balancing etc.

I use Nginx as an SSL terminator, load balancer, and static content web server.

The webserver is lightweight, easy to setup, and highly configurable.

NGINX as reverse proxy, designed to redirect traffic for correctly container.

Web Proxy working in front of Gunicorn

All my web servers are powered by NGINX.

An excellent Webserver simple to configure with high performances

Used nginx as exactly what it is great for: serving static content in a cache-friendly, load balanced manner.

It is exclusively for production web page hosting, we don't use nginx internally, only on the public-facing versions of static sites / Angular & Backbone/Marionette applications.

We use nginx to route web requests into Docker containers.

We have mono run in it using hyper fast cgi.

Proxy filtering Dumpster to port 80, making the WebUI easily accessible.

Nginx is used as a web proxy.

NGINX acts as the gateway server, decoding TLS and load balancing requests to the various downstream servers.

Our standard option for all HTTP and SSL work.

Reverse proxy and asset serving.

HTTPS Webserver

Fast serving of static assets.

Reverse proxy

Web Server

My preferred web server. Updated more often than other competitors, and was the first web server I was introduced to when creating Django apps.

ssl 설치까지 가능합니다. 하지만, 아직 더 학습이 필요하다고 판단됩니다.

Proxy, SSL termination, server directory browsing, whatever you can think of it gives.

Application web server and SSL terminator.

nginx is used in a pretty straightforward manner to promote http to https and convert www.cloak.ly to cloak.ly

Proxy-inverso sirviendo la aplicación ITBID

Reverse Proxy in front of the Tumbo App

Centos

Fast scalable webservers.

nginx serves static files and is used as reverse proxy for nodejs backend

서버 Reverse Proxy 및 SSL 적용

Nginx is used as a proxy between all of our backend Docker services. It allows us to keep the SSL termination on a single service so we don't have the overhead being added to our Node.js processes.

Web server and cache.

NGINX reverse proxies node.js applications to Varnish and handles the serving of static files

With nginx we deploy all web content and use it as a reverse-proxy for unified ssl and encryption aswell as a burst-control and traffic filter for all web-traffic.

Our front-end server and reverse proxy

Docker nginx-proxy

basic

We use Nginx to serve all of the content from our DigitalOcean droplets.

It is used to execute PHP.

Web server

Web server we use everywhere.

All of our dynamic sites are hosted behind Nginx.

Web application server.

Experience with nginx as a reverse proxy for a number of backend projects (with SSL support). My personal website runs nginx in a Docker container.

This is used as our primary reverse proxy allowing us to bypass the firewall restrictions most of our users have by routing all our apis via layer 7.

NGINX sits in front of all of our web servers. It is fantastic at load balancing traffic as well as serving as a cache at times when under massive load. It's a robust tool that we're happy to have at the front lines of all Wirkn web apps.

Configured servers in conjunction with docker at chaordic

Great resources in spinning up proper configurations for proxying public URLs to local node apps and services, plus it's a very solid and fast webserver in general.

Serving HTTP Requests and Cache

Handles HTTP(s) requests for front and backend. Easy reverse proxy setup/config.

Super easy to use and configure for web hosting.

Compared to Apache, Nginx runs with a low footprint, and is relatively easy to configure.

Nginx's easy load balancing made it an essential part of this stack. The simple implementation of an SSL certificate also helped us a lot in this stack.

Reduce Node.js load by serving static files and Prerender.io for crawlers.

Nginx is used as a reverse-proxy and static asset server.

nginx acts as our main webserver, proxying all connections to our other servers (both Python servers and Go servers). We use nginx because it's crazy fast, and it's proven to be reliable for the entire time we've been using it.

Insanely fast and easy to setup with TLS certificates.

Web server

Used as a Load balancer and reverse proxy for Wildfly

upstream to docker containers
static file server

Our frontend server.

Web server.

Nginx is our edge load balancer and router.

We use nginx to serve static files and to proxy requests to other services. We use it because of it's remarkable performance and simple configuration.

反向代理服务器

负载均衡

I switched from apache a couple of years ago and have never looked back. Simple, Fast, Versatile!

We use NGINX as the front-end load-balancer and reverse-proxy. This helps us with caching as well as being able to easily manage SSL certificates and split off static assets to a CDN.

HTTP server to serve files in production

Nginx acts as HTTP proxy for web services

Used as part of site hosting (Firebase HTTP Hosting manages implementation)

• 웹서버 구축

• 개발 환경 구축을 위해서 리버스 프록시 설정을 주어 포트별로 서비스를 서브 도메인 매핑하여 처리

Web Server for Reverse Proxy

As frontend

Load balancing

nginx web server with uWSGI for serving Flask application to view the connected nodes.

The web server that runs in front of our web services

Frontend is handled by nginx. Selected for its lightweight and speed.

NGINX is great at supporting lots of fast HTTP requests. We've typically used Apache to host websites, but use NGINX where it proves beneficial for other services.

Blazing speed.

As reverse proxy.

Nginx serves cached resources at lightening speeds while providing robust load balancing to Hndhld's worldwide app servers.

Not my forte, but nginx was easy to implement in this project. Currently this implementation is serving two domains in the same server. :P

Web Server

We use nginx as the main http/https services of our service

Nginx is used as reverse proxy for https://shiro.host/, our public development and testing server.

PrometheanTV uses nginx in a number of our back-end applications and services. Used primarily as reverse proxy or for routing and/or security needs.

API purposes

Our go-to Ruby application server.

Our super server that runs a web instance and a worker instance.

Rolling deploys are awesome! We use Unicorn to keep downtime to a minimum as we iterate quickly for our clients.

I use with my Ruby on Rails projects.