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. Apache Tomcat vs Puma

Apache Tomcat vs Puma

OverviewDecisionsComparisonAlternatives

Overview

Puma
Puma
Stacks1.2K
Followers265
Votes20
GitHub Stars7.8K
Forks1.5K
Apache Tomcat
Apache Tomcat
Stacks16.9K
Followers12.6K
Votes201
GitHub Stars8.0K
Forks5.3K

Apache Tomcat vs Puma: What are the differences?

Introduction

Apache Tomcat and Puma are both popular web servers used for hosting and managing web applications. While they share some similarities, there are key differences that set them apart.

  1. Deployment Model: Apache Tomcat is primarily designed for Java applications and supports Java Servlets and JavaServer Pages (JSP). It provides a lightweight environment for running Java-based web applications. On the other hand, Puma is a web server designed for Ruby applications, specifically Ruby on Rails. It provides a robust and high-performance platform for hosting Ruby web applications.

  2. Concurrency Model: Apache Tomcat uses a thread per request model, where each incoming request is handled by a separate thread. This makes it capable of handling multiple requests concurrently. Puma, on the other hand, uses a hybrid concurrency model with multiple worker processes and threads within each process. This allows Puma to handle a higher number of concurrent requests while utilizing system resources more efficiently.

  3. Scalability: When it comes to scalability, Apache Tomcat supports clustering and load balancing, allowing you to distribute the load across multiple instances of Tomcat servers. This helps in achieving higher availability and better performance for your applications. Puma, on the other hand, does not natively support clustering and load balancing. However, it can be used with other tools and technologies like Nginx or AWS Elastic Load Balancer to achieve similar scalability.

  4. Configuration and Tuning: Apache Tomcat provides a range of configuration options and tuning parameters that allow you to optimize its performance and behavior. It also supports features like session persistence, connection pooling, and resource caching. Puma, being a web server for Ruby applications, relies more on the configuration and optimization of the Ruby on Rails framework itself. It provides fewer server-specific tuning options compared to Tomcat.

  5. Operating System Compatibility: Apache Tomcat is written in Java and is platform-independent, making it compatible with a wide range of operating systems, including Windows, Linux, and macOS. Puma, on the other hand, is specifically designed for Unix-based systems like Linux and macOS. While it can be used on Windows systems, it is not as well optimized for that platform.

  6. Ecosystem and Community: Both Apache Tomcat and Puma have large and active communities supporting them. However, Apache Tomcat has a larger ecosystem and community due to its longstanding presence and popularity. It has a wide range of documentation, tutorials, and community-driven plugins and libraries available. Puma, being more focused on Ruby applications, has a slightly smaller ecosystem but still benefits from the vibrant Ruby community.

In Summary, Apache Tomcat and Puma differ in terms of their deployment model, concurrency model, scalability options, configuration and tuning abilities, operating system compatibility, and ecosystem size.

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 Puma, Apache Tomcat

Hari
Hari

Mar 3, 2020

Needs advice

I was in a situation where I have to configure 40 RHEL servers 20 each for Apache HTTP Server and Tomcat server. My task was to

  1. configure LVM with required logical volumes, format and mount for HTTP and Tomcat servers accordingly.
  2. Install apache and tomcat.
  3. Generate and apply selfsigned certs to http server.
  4. Modify default ports on Tomcat to different ports.
  5. Create users on RHEL for application support team.
  6. other administrative tasks like, start, stop and restart HTTP and Tomcat services.

I have utilized the power of ansible for all these tasks, which made it easy and manageable.

419k views419k
Comments
Mark
Mark

Software Developer at Nouveta

Mar 4, 2022

Needs adviceonRailsRailsRubyRubyPumaPuma

I have an integration service that pulls data from third party systems saves it and returns it to the user of the service. We can pull large data sets with the service and response JSON can go up to 5MB with gzip compression. I currently use Rails 6 and Ruby 2.7.2 and Puma web server. Slow clients tend to prevent other users from accessing the system. Am considering a switch to Unicorn.

38.4k views38.4k
Comments

Detailed Comparison

Puma
Puma
Apache Tomcat
Apache Tomcat

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.

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

Statistics
GitHub Stars
7.8K
GitHub Stars
8.0K
GitHub Forks
1.5K
GitHub Forks
5.3K
Stacks
1.2K
Stacks
16.9K
Followers
265
Followers
12.6K
Votes
20
Votes
201
Pros & Cons
Pros
  • 4
    Free
  • 3
    Easy
  • 3
    Convenient
  • 2
    Default Rails server
  • 2
    Consumes less memory than Unicorn
Cons
  • 0
    Uses `select` (limited client count)
Pros
  • 79
    Easy
  • 72
    Java
  • 49
    Popular
  • 1
    Spring web
Cons
  • 3
    Blocking - each http request block a thread
  • 2
    Easy to set up

What are some alternatives to Puma, Apache Tomcat?

NGINX

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.

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.

Passenger

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.

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.

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