Puma vs Wildfly

Overview

Puma

Stacks1.2K

Followers265

Votes20

GitHub Stars7.8K

Forks1.5K

Wildfly

Stacks187

Followers226

Votes6

Puma vs Wildfly: What are the differences?

Introduction

Puma and Wildfly are both popular application servers used for hosting web applications. These servers have their unique features and functions that differentiate them from each other.

Programming Language Support: Puma is designed specifically for Ruby applications and has built-in support for running Ruby code efficiently. Wildfly, on the other hand, is tailored for Java applications and provides a comprehensive Java EE stack for running enterprise-level applications.
Concurrency Model: Puma utilizes a multi-threaded concurrency model where each worker process handles multiple concurrent requests. In contrast, Wildfly uses a multi-process model where each request is handled by a separate thread within the server's pool of threads.
Deployment Options: Puma is commonly used in conjunction with web servers like Nginx or Apache, acting as a backend server. Wildfly, on the other hand, is a standalone application server that can handle HTTP requests directly without the need for an additional web server.
Configuration and Administration: Puma is known for its simplicity in configuration, making it easier for developers to set up and manage. Wildfly, being an enterprise-level application server, offers a wide range of configuration options and administrative features for complex deployment scenarios.
Community Support and Ecosystem: Puma benefits from the vibrant Ruby community, which provides extensive resources, plugins, and support for developers. Wildfly, being a Java-based server, has strong backing from the Java community and offers integration with various Java frameworks and libraries.
Scalability and Performance: Puma is lightweight and optimized for high performance, making it suitable for small to medium-sized applications with moderate traffic. Wildfly, with its robust Java EE stack, is designed for scalability and can efficiently handle large-scale enterprise applications with high traffic volumes.

In Summary, Puma and Wildfly differ in terms of their supported programming languages, concurrency models, deployment options, configuration/administration complexity, community support, and scalability/performance capabilities.

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)

Manual

Detailed Comparison

Puma	Wildfly
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.	It is a flexible, lightweight, managed application runtime that helps you build amazing applications. It supports the latest standards for web development.
Statistics
GitHub Stars 7.8K	GitHub Stars -
GitHub Forks 1.5K	GitHub Forks -
Stacks 1.2K	Stacks 187
Followers 265	Followers 226
Votes 20	Votes 6
Pros & Cons
Pros 4 Free 3 Convenient 3 Easy 2 First-class support for WebSockets 2 Multithreaded Cons 0 Uses `select` (limited client count)	Pros 3 Eclipse integration 3 Java
Integrations
No integrations available	IntelliJ IDEA Eclipse

What are some alternatives to Puma, Wildfly?

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

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

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 powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.

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

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.

Related Comparisons

Puma vs Wildfly: What are the differences?

Introduction

Puma and Wildfly are both popular application servers used for hosting web applications. These servers have their unique features and functions that differentiate them from each other.

Programming Language Support: Puma is designed specifically for Ruby applications and has built-in support for running Ruby code efficiently. Wildfly, on the other hand, is tailored for Java applications and provides a comprehensive Java EE stack for running enterprise-level applications.
Concurrency Model: Puma utilizes a multi-threaded concurrency model where each worker process handles multiple concurrent requests. In contrast, Wildfly uses a multi-process model where each request is handled by a separate thread within the server's pool of threads.
Deployment Options: Puma is commonly used in conjunction with web servers like Nginx or Apache, acting as a backend server. Wildfly, on the other hand, is a standalone application server that can handle HTTP requests directly without the need for an additional web server.
Configuration and Administration: Puma is known for its simplicity in configuration, making it easier for developers to set up and manage. Wildfly, being an enterprise-level application server, offers a wide range of configuration options and administrative features for complex deployment scenarios.
Community Support and Ecosystem: Puma benefits from the vibrant Ruby community, which provides extensive resources, plugins, and support for developers. Wildfly, being a Java-based server, has strong backing from the Java community and offers integration with various Java frameworks and libraries.
Scalability and Performance: Puma is lightweight and optimized for high performance, making it suitable for small to medium-sized applications with moderate traffic. Wildfly, with its robust Java EE stack, is designed for scalability and can efficiently handle large-scale enterprise applications with high traffic volumes.

Puma vs Wildfly

Overview