Get Advice Icon

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

lighttpd
lighttpd

104
37
+ 1
23
Puma
Puma

260
147
+ 1
16
Add tool

lighttpd vs Puma: What are the differences?

What is lighttpd? A secure, fast, compliant, and very flexible web-server that has been optimized for high-performance environments. 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.

What is Puma? A Modern, Concurrent Web Server for Ruby. 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.

lighttpd and Puma belong to "Web Servers" category of the tech stack.

"Lightweight" is the top reason why over 6 developers like lighttpd, while over 2 developers mention "Easy" as the leading cause for choosing Puma.

Puma is an open source tool with 5.78K GitHub stars and 987 GitHub forks. Here's a link to Puma's open source repository on GitHub.

Yammer, Product Hunt, and GrowthHackers are some of the popular companies that use Puma, whereas lighttpd is used by WhatsApp, Frame, and Fusionbox. Puma has a broader approval, being mentioned in 73 company stacks & 30 developers stacks; compared to lighttpd, which is listed in 15 company stacks and 4 developer stacks.

- No public GitHub repository available -

What is 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.

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.
Get Advice Icon

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

Why do developers choose lighttpd?
Why do developers choose Puma?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    What companies use lighttpd?
    What companies use Puma?

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

    What tools integrate with lighttpd?
    What tools integrate with Puma?
      No integrations found
      What are some alternatives to lighttpd and Puma?
      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.
      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.
      OpenResty
      OpenResty (aka. ngx_openresty) is a full-fledged web application server by bundling the standard Nginx core, lots of 3rd-party Nginx modules, as well as most of their external dependencies.
      See all alternatives
      Decisions about lighttpd and Puma
      Jerome Dalbert
      Jerome Dalbert
      Senior Backend Engineer at StackShare | 6 upvotes 94.4K views
      atStackShareStackShare
      Unicorn
      Unicorn
      Puma
      Puma
      Rails
      Rails

      We switched from Unicorn (process model) to Puma (threaded model) to decrease the memory footprint of our Rails production web server. Memory indeed dropped from 6GB to only 1GB!

      We just had to decrease our worker count and increase our thread count instead. Performance (response time and throughput) remained the same, if not slightly better. We had no thread-safety errors, which was good.

      Free bonus points are:

      • Requests are blazing fast on our dev and staging environments!
      • Puma has first-class support for WebSockets, so we know for sure that Rails ActionCable or GraphQL subscriptions will work great.
      • Being on Puma makes us even more "default Rails"-compliant since it is the default Rails web server these days.
      See more
      Interest over time
      Reviews of lighttpd and Puma
      No reviews found
      How developers use lighttpd and Puma
      Avatar of Jan Hoekstra
      Jan Hoekstra uses lighttpdlighttpd

      Lightweight with built-in support for CGI scripts.

      Avatar of Oded Arbel
      Oded Arbel uses PumaPuma

      Server for Rails-powered API

      Avatar of Satoru Ishikawa
      Satoru Ishikawa uses PumaPuma

      Heroku 銇у嫊銇嬨仚Web銈点兗銉愩兗

      Avatar of Jamie Yun
      Jamie Yun uses PumaPuma

      expert

      How much does lighttpd cost?
      How much does Puma cost?
      Pricing unavailable
      Pricing unavailable
      News about lighttpd
      More news