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.
What is lighttpd?
What is Puma?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using lighttpd?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Puma?
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.