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. Microsoft IIS vs Puma

Microsoft IIS vs Puma

OverviewDecisionsComparisonAlternatives

Overview

Puma
Puma
Stacks1.2K
Followers265
Votes20
GitHub Stars7.8K
Forks1.5K
Microsoft IIS
Microsoft IIS
Stacks15.5K
Followers7.7K
Votes236

Microsoft IIS vs Puma: What are the differences?

# Introduction

1. **Scalability**:
   Microsoft IIS is more suited for large scale enterprise applications due to its ability to handle a high volume of traffic efficiently, while Puma is more commonly used for smaller to medium-sized applications.
2. **Supported platforms**:
   Microsoft IIS is primarily designed to run on Windows servers, while Puma is designed to work on Unix-based systems like Linux.
3. **Language support**:
   Microsoft IIS is optimized for hosting applications built on the .NET framework, while Puma is more commonly used for hosting Ruby applications.
4. **Configuration flexibility**:
   Microsoft IIS offers a more user-friendly graphical interface for configuration, while Puma requires more manual configuration through code or configuration files.
5. **Resource consumption**:
   Microsoft IIS tends to consume more system resources compared to Puma, making it less efficient in terms of resource utilization.
6. **Community support**:
   Puma has a more active open-source community that regularly contributes to its development and provides support, whereas Microsoft IIS has more official support channels provided by Microsoft.

In Summary, Microsoft IIS and Puma differ in terms of scalability, supported platforms, language support, configuration flexibility, resource consumption, and community support.

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, Microsoft IIS

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

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.

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.

Statistics
GitHub Stars
7.8K
GitHub Stars
-
GitHub Forks
1.5K
GitHub Forks
-
Stacks
1.2K
Stacks
15.5K
Followers
265
Followers
7.7K
Votes
20
Votes
236
Pros & Cons
Pros
  • 4
    Free
  • 3
    Easy
  • 3
    Convenient
  • 2
    Consumes less memory than Unicorn
  • 2
    Multithreaded
Cons
  • 0
    Uses `select` (limited client count)
Pros
  • 83
    Great with .net
  • 55
    I'm forced to use iis
  • 27
    Use nginx
  • 18
    Azure integration
  • 15
    Best for ms technologyes ms bullshit
Cons
  • 1
    Hard to set up

What are some alternatives to Puma, Microsoft IIS?

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.

Apache Tomcat

Apache Tomcat

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

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