NGINX vs Passenger vs Puma

Need advice about which tool to choose?Ask the StackShare community!

NGINX

88.6K
39.5K
+ 1
5.5K
Passenger

1.4K
262
+ 1
199
Puma

367
221
+ 1
19
Advice on NGINX, Passenger, and Puma

I am diving into web development, both front and back end. I feel comfortable with administration, scripting and moderate coding in bash, Python and C++, but I am also a Windows fan (i love inner conflict). What are the votes on web servers? IIS is expensive and restrictive (has Windows adoption of open source changed this?) Apache has the history but seems to be at the root of most of my Infosec issues, and I know nothing about nginx (is it too new to rely on?). And no, I don't know what I want to do on the web explicitly, but hosting and data storage (both cloud and tape) are possibilities. Ready, aim fire!

See more
Replies (1)
Simon Aronsson
Developer Advocate at k6 / Load Impact · | 3 upvotes · 146.1K views
Recommends
NGINX

I would pick nginx over both IIS and Apace HTTP Server any day. Combine it with docker, and as you grow maybe even traefik, and you'll have a really flexible solution for serving http content where you can take sites and projects up and down without effort, easily move it between systems and dont have to handle any dependencies on your actual local machine.

See more
Needs advice
on
Apache HTTP Server
and
NGINX

From a StackShare Community member: "We are a LAMP shop currently focused on improving web performance for our customers. We have made many front-end optimizations and now we are considering replacing Apache with nginx. I was wondering if others saw a noticeable performance gain or any other benefits by switching."

See more
Replies (3)
Recommends
NGINX

I use nginx because it is very light weight. Where Apache tries to include everything in the web server, nginx opts to have external programs/facilities take care of that so the web server can focus on efficiently serving web pages. While this can seem inefficient, it limits the number of new bugs found in the web server, which is the element that faces the client most directly.

See more
Leandro Barral
Recommends
NGINX

I use nginx because its more flexible and easy to configure

See more
Christian Cwienk
Software Developer at SAP · | 1 upvotes · 138.9K views

I use Apache HTTP Server because it's intuitive, comprehensive, well-documented, and just works

See more
View all (3)
Decisions about NGINX, Passenger, and Puma
Daniel Calvo
Co-Founder at Polpo Data Analytics & Software Development · | 5 upvotes · 6.6K views

For us, NGINX is a lite HTTP server easy to configure. On our research, we found a well-documented software we a lot of support from the community.

We have been using it alongside tools like certbot and it has been a total success.

We can easily configure our sites and have a folder for available vs enabled sites, and with the nginx -t command we can easily check everything is running fine.

See more
Grant Steuart
  • Server rendered HTML output from PHP is being migrated to the client as Vue.js components, future plans to provide additional content, and other new miscellaneous features all result in a substantial increase of static files needing to be served from the server. NGINX has better performance than Apache for serving static content.
  • The change to NGINX will require switching from PHP to PHP-FPM resulting in a distributed architecture with a higher complexity configuration, but this is outweighed by PHP-FPM being faster than PHP for processing requests.
  • The NGINX + PHP-FPM setup now allows for horizontally scaling of resources rather vertically scaling the previously combined Apache + PHP resources.
  • PHP shell tasks can now efficiently be decoupled from the application reducing main application footprint and allow for scaling of tasks on an individual basis.
See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of NGINX
Pros of Passenger
Pros of Puma
  • 1.5K
    High-performance http server
  • 899
    Performance
  • 730
    Easy to configure
  • 606
    Open source
  • 529
    Load balancer
  • 286
    Scalability
  • 285
    Free
  • 222
    Web server
  • 174
    Simplicity
  • 133
    Easy setup
  • 29
    Content caching
  • 19
    Web Accelerator
  • 14
    Capability
  • 13
    Fast
  • 11
    Predictability
  • 10
    High-latency
  • 6
    Reverse Proxy
  • 6
    Fast and lightweight
  • 6
    Supports http/2
  • 4
    The best of them
  • 4
    Lots of Modules
  • 4
    Great Community
  • 4
    Enterprise version
  • 3
    Embedded Lua scripting
  • 3
    Reversy Proxy
  • 3
    Streaming media delivery
  • 3
    Streaming media
  • 3
    High perfomance proxy server
  • 2
    Lightweight
  • 2
    saltstack
  • 2
    Fast and easy to set up
  • 2
    Slim
  • 1
    GRPC-Web
  • 1
    Narrow focus. Easy to configure. Fast
  • 1
    Ingress controller
  • 1
    Along with Redis Cache its the Most superior
  • 1
    Virtual hosting
  • 0
    A
  • 43
    Nginx integration
  • 36
    Great for rails
  • 21
    Fast web server
  • 19
    Free
  • 15
    Lightweight
  • 14
    Scalable
  • 13
    Rolling restarts
  • 10
    Multithreading
  • 9
    Out-of-process architecture
  • 6
    Low-bandwidth
  • 2
    Virtually infinitely scalable
  • 2
    Deployment error resistance
  • 2
    Mass deployment
  • 2
    High-latency
  • 1
    Many of its good features are only enterprise level
  • 1
    Apache integration
  • 1
    Secure
  • 1
    Asynchronous I/O
  • 1
    Multiple programming language support
  • 3
    Convenient
  • 3
    Free
  • 3
    Easy
  • 2
    Multithreaded
  • 2
    Default Rails server
  • 2
    First-class support for WebSockets
  • 2
    Consumes less memory than Unicorn
  • 1
    Lightweight
  • 1
    Fast

Sign up to add or upvote prosMake informed product decisions

Cons of NGINX
Cons of Passenger
Cons of Puma
  • 7
    Advanced features require subscription
  • 0
    Cost (some features require paid/pro)
  • 0
    Uses `select` (limited client count)

Sign up to add or upvote consMake informed product decisions

What is NGINX?

nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018.

What is Passenger?

Phusion Passenger is a web server and application server, designed to be fast, robust and lightweight. It takes a lot of complexity out of deploying web apps, adds powerful enterprise-grade features that are useful in production, and makes administration much easier and less complex.

What is Puma?

Unlike other Ruby Webservers, Puma was built for speed and parallelism. Puma is a small library that provides a very fast and concurrent HTTP 1.1 server for Ruby web applications.

Need advice about which tool to choose?Ask the StackShare community!

What companies use NGINX?
What companies use Passenger?
What companies use Puma?

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with NGINX?
What tools integrate with Passenger?
What tools integrate with Puma?
    No integrations found

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    What are some alternatives to NGINX, Passenger, and Puma?
    HAProxy
    HAProxy (High Availability Proxy) is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
    lighttpd
    lighttpd has a very low memory footprint compared to other webservers and takes care of cpu-load. Its advanced feature-set (FastCGI, CGI, Auth, Output-Compression, URL-Rewriting and many more) make lighttpd the perfect webserver-software for every server that suffers load problems.
    Traefik
    A modern HTTP reverse proxy and load balancer that makes deploying microservices easy. Traefik integrates with your existing infrastructure components and configures itself automatically and dynamically.
    Caddy
    Caddy 2 is a powerful, enterprise-ready, open source web server with automatic HTTPS written in Go.
    Envoy
    Originally built at Lyft, Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures.
    See all alternatives
    How developers use NGINX, Passenger, and Puma
    MaxCDN uses
    NGINX

    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.

    Cloudcraft uses
    NGINX

    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.

    datapile uses
    NGINX

    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.

    SIA Monkey See Monkey Do uses
    NGINX

    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.

    Wirkn Inc. uses
    NGINX

    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.

    pludoni GmbH uses
    Passenger

    "deploy + forget" application deployment with good default configuration.

    Trustroots uses
    Passenger

    Serving NodeJS app together with Nginx.

    Oded Arbel uses
    Puma

    Server for Rails-powered API

    Satoru Ishikawa uses
    Puma

    Heroku で動かすWebサーバー

    Jamie Yun uses
    Puma

    expert