StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Platform as a Service
  4. Web Servers
  5. Passenger vs Puma vs nginx

Passenger vs Puma vs nginx

OverviewDecisionsComparisonAlternatives

Overview

NGINX
NGINX
Stacks115.0K
Followers61.9K
Votes5.5K
GitHub Stars28.4K
Forks7.6K
Passenger
Passenger
Stacks1.4K
Followers298
Votes199
GitHub Stars5.1K
Forks557
Puma
Puma
Stacks1.2K
Followers265
Votes20
GitHub Stars7.8K
Forks1.5K

Passenger vs Puma vs nginx: What are the differences?

Introduction

Passenger, Puma, and Nginx are popular web servers used in deploying Ruby on Rails applications. Each has its own set of strengths and differences that make them suitable for different use cases.

  1. Scalability: Passenger is a multi-process web server that can handle high concurrency by spinning up multiple application processes. Puma, on the other hand, is a multi-threaded web server, allowing it to handle high traffic by utilizing threads within a single process. Nginx, as a reverse proxy server, can distribute incoming requests among multiple backend servers, providing load balancing capabilities for scalability.

  2. Memory Usage: Passenger typically consumes more memory due to running multiple processes, which can lead to higher memory usage compared to Puma. Puma, being multi-threaded, has a more efficient memory footprint as it shares resources within a single process. Nginx is known for its low memory usage, especially when serving static content, making it a lightweight option for handling incoming requests.

  3. Configuration Complexity: Passenger provides a more straightforward configuration setup, making it easier for beginners to set up and deploy Ruby on Rails applications. Puma offers more advanced configuration options for optimization and customization but may require more expertise to configure effectively. Nginx requires separate configurations for load balancing, caching, and SSL termination, adding another layer of complexity but granting more granular control over server behavior.

  4. Performance: Passenger is known for its ease of use and reliable performance, making it suitable for small to medium-sized applications. Puma's multi-threaded architecture can provide better performance for I/O-bound applications that benefit from concurrency. Nginx excels in serving static content efficiently and handling high traffic volumes due to its event-driven, asynchronous architecture.

  5. Logging and Monitoring: Passenger offers built-in monitoring tools to track application performance and server health, providing insights into request throughput and memory usage. Puma provides detailed logs for requests and error responses, allowing for easy troubleshooting and performance analysis. Nginx has extensive logging capabilities to track incoming requests, upstream server responses, and server errors, offering visibility into server activities and potential issues.

  6. Supported Protocols: Passenger supports various application servers, such as Ruby, Python, and Node.js, making it versatile for different programming languages. Puma is specifically designed for Ruby applications, optimizing performance and compatibility with Ruby on Rails frameworks. Nginx supports multiple protocols, including HTTP, HTTPS, and WebSocket, allowing for flexible communication options and secure connections for web applications.

In Summary, Passenger, Puma, and Nginx offer distinct features in terms of scalability, memory usage, configuration complexity, performance, logging, monitoring, and supported protocols, catering to different requirements in deploying Ruby on Rails applications.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on NGINX, Passenger, Puma

Daniel
Daniel

Co-Founder at Polpo Data Analytics & Software Development

May 25, 2021

Decided

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.

289k views289k
Comments
greg00m
greg00m

Mar 9, 2020

Needs advice

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!

766k views766k
Comments
Grant
Grant

Developer at GMS LLC

Sep 5, 2020

Decided
  • 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.
429k views429k
Comments

Detailed Comparison

NGINX
NGINX
Passenger
Passenger
Puma
Puma

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.

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.

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.

Statistics
GitHub Stars
28.4K
GitHub Stars
5.1K
GitHub Stars
7.8K
GitHub Forks
7.6K
GitHub Forks
557
GitHub Forks
1.5K
Stacks
115.0K
Stacks
1.4K
Stacks
1.2K
Followers
61.9K
Followers
298
Followers
265
Votes
5.5K
Votes
199
Votes
20
Pros & Cons
Pros
  • 1453
    High-performance http server
  • 895
    Performance
  • 730
    Easy to configure
  • 607
    Open source
  • 530
    Load balancer
Cons
  • 10
    Advanced features require subscription
Pros
  • 43
    Nginx integration
  • 36
    Great for rails
  • 21
    Fast web server
  • 19
    Free
  • 15
    Lightweight
Cons
  • 0
    Cost (some features require paid/pro)
Pros
  • 4
    Free
  • 3
    Convenient
  • 3
    Easy
  • 2
    Default Rails server
  • 2
    First-class support for WebSockets
Cons
  • 0
    Uses `select` (limited client count)
Integrations
No integrations available
Python
Python
Ruby
Ruby
Apache HTTP Server
Apache HTTP Server
Node.js
Node.js
Meteor
Meteor
No integrations available

What are some alternatives to NGINX, Passenger, Puma?

Apache HTTP Server

Apache HTTP Server

The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet.

Unicorn

Unicorn

Unicorn is an HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. Slow clients should only be served by placing a reverse proxy capable of fully buffering both the the request and response in between Unicorn and slow clients.

Microsoft IIS

Microsoft IIS

Internet Information Services (IIS) for Windows Server is a flexible, secure and manageable Web server for hosting anything on the Web. From media streaming to web applications, IIS's scalable and open architecture is ready to handle the most demanding tasks.

Apache Tomcat

Apache Tomcat

Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.

Gunicorn

Gunicorn

Gunicorn is a pre-fork worker model ported from Ruby's Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

Jetty

Jetty

Jetty is used in a wide variety of projects and products, both in development and production. Jetty can be easily embedded in devices, tools, frameworks, application servers, and clusters. See the Jetty Powered page for more uses of Jetty.

lighttpd

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.

Swoole

Swoole

It is an open source high-performance network framework using an event-driven, asynchronous, non-blocking I/O model which makes it scalable and efficient.

Caddy

Caddy

Caddy 2 is a powerful, enterprise-ready, open source web server with automatic HTTPS written in Go.

Cowboy

Cowboy

Cowboy aims to provide a complete HTTP stack in a small code base. It is optimized for low latency and low memory usage, in part because it uses binary strings. Cowboy provides routing capabilities, selectively dispatching requests to handlers written in Erlang.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase