Alternatives to Bull logo

Alternatives to Bull

Buffalo, Sidekiq, Hangfire, Resque, and Beanstalkd are the most popular alternatives and competitors to Bull.
56
99
+ 1
4

What is Bull and what are its top alternatives?

The fastest, most reliable, Redis-based queue for Node. Carefully written for rock solid stability and atomicity.
Bull is a tool in the Background Processing category of a tech stack.
Bull is an open source tool with 12.4K GitHub stars and 1.3K GitHub forks. Here’s a link to Bull's open source repository on GitHub

Top Alternatives to Bull

  • Buffalo
    Buffalo

    Buffalo is Go web framework. Yeah, I hate the word "framework" too! Buffalo is different though. Buffalo doesn't want to re-invent wheels like routing and templating. Buffalo is glue that wraps all of the best packages available and makes them all play nicely together. ...

  • Sidekiq
    Sidekiq

    Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background processing dead simple. ...

  • Hangfire
    Hangfire

    It is an open-source framework that helps you to create, process and manage your background jobs, i.e. operations you don't want to put in your request processing pipeline. It supports all kind of background tasks – short-running and long-running, CPU intensive and I/O intensive, one shot and recurrent. ...

  • Resque
    Resque

    Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or you can create new classes specifically to do work. Or, you can do both. ...

  • Beanstalkd
    Beanstalkd

    Beanstalks's interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously. ...

  • PHP-FPM
    PHP-FPM

    It is an alternative PHP FastCGI implementation with some additional features useful for sites of any size, especially busier sites. It includes Adaptive process spawning, Advanced process management with graceful stop/start, Emergency restart in case of accidental opcode cache destruction etc. ...

  • delayed_job
    delayed_job

    Delayed_job (or DJ) encapsulates the common pattern of asynchronously executing longer tasks in the background. It is a direct extraction from Shopify where the job table is responsible for a multitude of core tasks. ...

  • Kue
    Kue

    Kue is a feature rich priority job queue for node.js backed by redis. A key feature of Kue is its clean user-interface for viewing and managing queued, active, failed, and completed jobs. ...

Bull alternatives & related posts

Buffalo logo

Buffalo

12
42
5
MVC Web Framework for Go
12
42
+ 1
5
PROS OF BUFFALO
  • 4
    Go
  • 1
    Friendly Api
CONS OF BUFFALO
    Be the first to leave a con

    related Buffalo posts

    Sidekiq logo

    Sidekiq

    1.1K
    566
    407
    Simple, efficient background processing for Ruby
    1.1K
    566
    + 1
    407
    PROS OF SIDEKIQ
    • 123
      Simple
    • 99
      Efficient background processing
    • 60
      Scalability
    • 37
      Better then resque
    • 26
      Great documentation
    • 15
      Admin tool
    • 14
      Great community
    • 8
      Integrates with redis automatically, with zero config
    • 7
      Great support
    • 7
      Stupidly simple to integrate and run on Rails/Heroku
    • 3
      Freeium
    • 3
      Ruby
    • 2
      Pro version
    • 1
      Fast
    • 1
      Dashboard w/live polling
    • 1
      Great ecosystem of addons
    CONS OF SIDEKIQ
      Be the first to leave a con

      related Sidekiq posts

      Cyril Duchon-Doris

      We decided to use AWS Lambda for several serverless tasks such as

      • Managing AWS backups
      • Processing emails received on Amazon SES and stored to Amazon S3 and notified via Amazon SNS, so as to push a message on our Redis so our Sidekiq Rails workers can process inbound emails
      • Pushing some relevant Amazon CloudWatch metrics and alarms to Slack
      See more

      I'm building a new process management tool. I decided to build with Rails as my backend, using Sidekiq for background jobs. I chose to work with these tools because I've worked with them before and know that they're able to get the job done. They may not be the sexiest tools, but they work and are reliable, which is what I was optimizing for. For data stores, I opted for PostgreSQL and Redis. Because I'm planning on offering dashboards, I wanted a SQL database instead of something like MongoDB that might work early on, but be difficult to use as soon as I want to facilitate aggregate queries.

      On the front-end I'm using Vue.js and vuex in combination with #Turbolinks. In effect, I want to render most pages on the server side without key interactions being managed by Vue.js . This is the first project I'm working on where I've explicitly decided not to include jQuery . I have found React and Redux.js more confusing to setup. I appreciate the opinionated approach from the Vue.js community and that things just work together the way that I'd expect. To manage my javascript dependencies, I'm using Yarn .

      For CSS frameworks, I'm using #Bulma.io. I really appreciate it's minimal nature and that there are no hard javascript dependencies. And to add a little spice, I'm using #font-awesome.

      See more
      Hangfire logo

      Hangfire

      173
      182
      17
      Perform background processing in .NET and .NET Core applications
      173
      182
      + 1
      17
      PROS OF HANGFIRE
      • 7
        Integrated UI dashboard
      • 5
        Simple
      • 3
        Robust
      • 2
        In Memory
      • 0
        Simole
      • 0
        Cons
      CONS OF HANGFIRE
        Be the first to leave a con

        related Hangfire posts

        Resque logo

        Resque

        111
        109
        9
        A Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later
        111
        109
        + 1
        9
        PROS OF RESQUE
        • 5
          Free
        • 3
          Scalable
        • 1
          Easy to use on heroku
        CONS OF RESQUE
          Be the first to leave a con

          related Resque posts

          Beanstalkd logo

          Beanstalkd

          108
          134
          74
          A simple, fast work queue
          108
          134
          + 1
          74
          PROS OF BEANSTALKD
          • 23
            Fast
          • 12
            Free
          • 12
            Does one thing well
          • 9
            Scalability
          • 8
            Simplicity
          • 3
            External admin UI developer friendly
          • 3
            Job delay
          • 2
            Job prioritization
          • 2
            External admin UI
          CONS OF BEANSTALKD
            Be the first to leave a con

            related Beanstalkd posts

            Frédéric MARAND
            Core Developer at OSInet · | 2 upvotes · 199.7K views

            I used Kafka originally because it was mandated as part of the top-level IT requirements at a Fortune 500 client. What I found was that it was orders of magnitude more complex ...and powerful than my daily Beanstalkd , and far more flexible, resilient, and manageable than RabbitMQ.

            So for any case where utmost flexibility and resilience are part of the deal, I would use Kafka again. But due to the complexities involved, for any time where this level of scalability is not required, I would probably just use Beanstalkd for its simplicity.

            I tend to find RabbitMQ to be in an uncomfortable middle place between these two extremities.

            See more
            PHP-FPM logo

            PHP-FPM

            99
            100
            0
            An alternative FastCGI daemon for PHP
            99
            100
            + 1
            0
            PROS OF PHP-FPM
              Be the first to leave a pro
              CONS OF PHP-FPM
                Be the first to leave a con

                related PHP-FPM posts

                delayed_job logo

                delayed_job

                48
                57
                6
                Database backed asynchronous priority queue -- Extracted from Shopify
                48
                57
                + 1
                6
                PROS OF DELAYED_JOB
                • 3
                  Easy to get started
                • 2
                  Reliable
                • 1
                  Doesn't require Redis
                CONS OF DELAYED_JOB
                  Be the first to leave a con

                  related delayed_job posts

                  Jerome Dalbert
                  Senior Backend Engineer at StackShare · | 4 upvotes · 77.6K views

                  delayed_job is a great Rails background job library for new projects, as it only uses what you already have: a relational database. We happily used it during the company’s first two years.

                  But it started to falter as our web and database transactions significantly grew. Our app interacted with users via SMS texts sent inside background jobs. Because the delayed_job daemon ran every couple seconds, this meant that users often waited several long seconds before getting text replies, which was not acceptable. Moreover, job processing was done inside AWS Elastic Beanstalk web instances, which were already under stress and not meant to handle jobs.

                  We needed a fast background job system that could process jobs in near real-time and integrate well with AWS. Sidekiq is a fast and popular Ruby background job library, but it does not leverage the Elastic Beanstalk worker architecture, and you have to maintain a Redis instance.

                  We ended up choosing active-elastic-job, which seamlessly integrates with worker instances and Amazon SQS. SQS is a fast queue and you don’t need to worry about infrastructure or scaling, as AWS handles it for you.

                  We noticed significant performance gains immediately after making the switch.

                  #BackgroundProcessing

                  See more
                  Jerome Dalbert
                  Senior Backend Engineer at StackShare · | 3 upvotes · 52.7K views

                  We use Sidekiq to process millions of Ruby background jobs a day under normal loads. We sometimes process more than that when running one-off backfill tasks.

                  With so many jobs, it wouldn't really make sense to use delayed_job, as it would put our main database under unnecessary load, which would make it a bottleneck with most DB queries serving jobs and not end users. I suppose you could create a separate DB just for jobs, but that can be a hassle. Sidekiq uses a separate Redis instance so you don't have this problem. And it is very performant!

                  I also like that its free version comes "batteries included" with:

                  • A web monitoring UI that provides some nice stats.
                  • An API that can come in handy for one-off tasks, like changing the queue of certain already enqueued jobs.

                  Sidekiq is a pleasure to use. All our engineers love it!

                  See more
                  Kue logo

                  Kue

                  33
                  83
                  2
                  Kue is a priority job queue backed by redis, built for node.js
                  33
                  83
                  + 1
                  2
                  PROS OF KUE
                  • 2
                    Simple
                  CONS OF KUE
                    Be the first to leave a con

                    related Kue posts