Sidekiq VS Puma

Compare Sidekiq vs Puma and see what are their differences.

Sidekiq

Simple, efficient background processing for Ruby (by sidekiq)

Puma

A Ruby/Rack web server built for parallelism (by puma)
Our great sponsors
  • PopRuby - Clothing and Accessories for Ruby Developers
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
Sidekiq Puma
88 40
12,913 7,573
0.7% 0.5%
8.9 8.7
2 days ago 7 days ago
Ruby Ruby
GNU Lesser General Public License v3.0 only BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

Sidekiq

Posts with mentions or reviews of Sidekiq. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-04.

Puma

Posts with mentions or reviews of Puma. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-21.
  • Breaking the 300 barrier
    3 projects | dev.to | 21 Feb 2024
    As we use Puma as our webserver for our rails application, I quickly went to Puma's config file which typically resides in config/puma.rb. The config was set as
  • Would you consider Rails as stable nowadays ?
    2 projects | /r/rails | 8 Dec 2023
    They do! It's in the first section of the readme on the repo:
    2 projects | /r/rails | 8 Dec 2023
  • Hosting Rails App on AWS
    2 projects | /r/rails | 27 Jun 2023
    Start with service with systemd
  • Could not detect rake tasks
    6 projects | /r/rails | 3 May 2023
    # Use the Puma web server [https://github.com/puma/puma] gem "puma", "~> 5.0" # Build JSON APIs with ease [https://github.com/rails/jbuilder] # gem "jbuilder" gem 'rack-cors' gem "devise" gem "jsonapi-serializer" gem 'devise-jwt' gem 'active_model_serializers' gem 'followability' gem 'dotenv-rails', groups: [:development, :test, :production] gem 'sprockets' # Use Redis adapter to run Action Cable in production # gem "redis", "~> 4.0" # Use Kredis to get higher-level data types in Redis [https://github.com/rails/kredis] # gem "kredis" # Use Active Model has_secure_password [https://guides.rubyonrails.org/active_model_basics.html#securepassword] # gem "bcrypt", "~> 3.1.7" # Windows does not include zoneinfo files, so bundle the tzinfo-data gem gem "tzinfo-data", platforms: %i[ mingw mswin x64_mingw jruby ] # Reduces boot times through caching; required in config/boot.rb gem "bootsnap", require: false # Use Active Storage variants [https://guides.rubyonrails.org/active_storage_overview.html#transforming-images] # gem "image_processing", "~> 1.2" # Use Rack CORS for handling Cross-Origin Resource Sharing (CORS), making cross-origin AJAX possible # gem "rack-cors" group :development, :test do # See https://guides.rubyonrails.org/debugging_rails_applications.html#debugging-with-the-debug-gem gem "debug", platforms: %i[ mri mingw x64_mingw ] end group :development do gem "sqlite3", "~> 1.4" # Speed up commands on slow machines / big apps [https://github.com/rails/spring] # gem "spring" end group :production do gem 'pg' end
  • Dusting off my rails knowledge, need some tips / guidance on rails 7 and production
    10 projects | /r/rails | 7 Apr 2023
    source "https://rubygems.org" git_source(:github) { |repo| "https://github.com/#{repo}.git" } ruby "3.1.0" # Bundle edge Rails instead: gem "rails", github: "rails/rails", branch: "main" gem "rails", "~> 7.0.4", ">= 7.0.4.2" # The original asset pipeline for Rails [https://github.com/rails/sprockets-rails] gem "sprockets-rails" # Use sqlite3 as the database for Active Record gem "sqlite3", "~> 1.4" # Use the Puma web server [https://github.com/puma/puma] gem "puma", "~> 5.0" # Use JavaScript with ESM import maps [https://github.com/rails/importmap-rails] gem "importmap-rails" # Hotwire's SPA-like page accelerator [https://turbo.hotwired.dev] gem "turbo-rails" # Hotwire's modest JavaScript framework [https://stimulus.hotwired.dev] gem "stimulus-rails" # Build JSON APIs with ease [https://github.com/rails/jbuilder] gem "jbuilder" gem "mongoid" gem "mongoid-grid_fs" gem 'bootstrap', '~> 5.2.2' #sourced from https://github.com/twbs/bootstrap-rubygem gem 'rack-cors' # Windows does not include zoneinfo files, so bundle the tzinfo-data gem gem "tzinfo-data", platforms: %i[ mingw mswin x64_mingw jruby ] # Reduces boot times through caching; required in config/boot.rb gem "bootsnap", require: false
  • Write your own Domain Specific Language in Ruby
    2 projects | dev.to | 6 Feb 2023
    That doesn't mean one excludes the other. Gems like Puma use the instance_eval method for their configuration file.
  • puma 6.0 released
    2 projects | /r/ruby | 21 Oct 2022
    Anyway I did it: https://github.com/puma/puma/issues/3003 It's quite more complicated: https://github.com/puma/puma/issues/2999 A fix is in progress: https://github.com/puma/puma/pull/3002
    2 projects | /r/ruby | 21 Oct 2022
  • Pitchfork: Rack HTTP server for shared-nothing architecture
    8 projects | news.ycombinator.com | 12 Oct 2022
    I'm the author of the original 'refork' feature introduced to Puma a couple years ago [1], that served as an inspiration for this project.

    As I understand it, Pitchfork is an implementation of a reforking feature on top of Unicorn, a single-threaded multi-process Rack HTTP server.

    The general idea of 'reforking' is that in addition to pre-forking worker processes at initialization time, you re-fork them on an ongoing basis, in order to optimize copy-on-write efficiency across processes, especially for memory allocations that might happen after initialization. The Pitchfork author mentions sharing YJIT machine code as a particularly important use-case [2], one that has become relevant in recent Ruby releases.

    I never saw much interest in the concept when I originally introduced the reforking feature to Puma, and it remained a kind of interesting experiment that never saw much production uptake. I'm thrilled that Shopify is iterating on the concept through this project and I hope the technique will continue to be refined and developed, and see broader adoption as a result.

    [1] https://github.com/puma/puma/pull/2099

What are some alternatives?

When comparing Sidekiq and Puma you can also consider the following projects:

Thin - A very fast & simple Ruby web server

falcon - A high-performance web server for Ruby, supporting HTTP/1, HTTP/2 and TLS.

Resque - Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.

Sneakers - A fast background processing framework for Ruby and RabbitMQ

Shoryuken - A super efficient Amazon SQS thread based message processor for Ruby

Sucker Punch - Sucker Punch is a Ruby asynchronous processing library using concurrent-ruby, heavily influenced by Sidekiq and girl_friday.

Phusion Passenger - A fast and robust web server and application server for Ruby, Python and Node.js

Apache Kafka - Mirror of Apache Kafka

celery - Distributed Task Queue (development branch)

Delayed::Job - Database based asynchronous priority queue system -- Extracted from Shopify

good_job - Multithreaded, Postgres-based, Active Job backend for Ruby on Rails.

Iodine - iodine - HTTP / WebSockets Server for Ruby with Pub/Sub support