Alternatives to Faktory logo

Alternatives to Faktory

Sidekiq, RabbitMQ, Resque, Beanstalkd, and Hangfire are the most popular alternatives and competitors to Faktory.
5
15
+ 1
2

What is Faktory and what are its top alternatives?

Redis -> Sidekiq == Faktory -> Faktory. Faktory is a server daemon which provides a simple API to produce and consume background jobs. Jobs are a small JSON hash with a few mandatory keys.
Faktory is a tool in the Background Processing category of a tech stack.
Faktory is an open source tool with 4.1K GitHub stars and 172 GitHub forks. Here’s a link to Faktory's open source repository on GitHub

Top Alternatives to Faktory

  • 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. ...

  • RabbitMQ

    RabbitMQ

    RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received. ...

  • 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. ...

  • 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. ...

  • 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. ...

  • Bull

    Bull

    The fastest, most reliable, Redis-based queue for Node. Carefully written for rock solid stability and atomicity. ...

Faktory alternatives & related posts

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

related RabbitMQ posts

James Cunningham
Operations Engineer at Sentry · | 18 upvotes · 1.1M views
Shared insights
on
Celery
RabbitMQ
at

As Sentry runs throughout the day, there are about 50 different offline tasks that we execute—anything from “process this event, pretty please” to “send all of these cool people some emails.” There are some that we execute once a day and some that execute thousands per second.

Managing this variety requires a reliably high-throughput message-passing technology. We use Celery's RabbitMQ implementation, and we stumbled upon a great feature called Federation that allows us to partition our task queue across any number of RabbitMQ servers and gives us the confidence that, if any single server gets backlogged, others will pitch in and distribute some of the backlogged tasks to their consumers.

#MessageQueue

See more
Tim Abbott
Shared insights
on
RabbitMQ
Python
Redis
at

We've been using RabbitMQ as Zulip's queuing system since we needed a queuing system. What I like about it is that it scales really well and has good libraries for a wide range of platforms, including our own Python. So aside from getting it running, we've had to put basically 0 effort into making it scale for our needs.

However, there's several things that could be better about it: * It's error messages are absolutely terrible; if ever one of our users ends up getting an error with RabbitMQ (even for simple things like a misconfigured hostname), they always end up needing to get help from the Zulip team, because the errors logs are just inscrutable. As an open source project, we've handled this issue by really carefully scripting the installation to be a failure-proof configuration (in this case, setting the RabbitMQ hostname to 127.0.0.1, so that no user-controlled configuration can break it). But it was a real pain to get there and the process of determining we needed to do that caused a significant amount of pain to folks installing Zulip. * The pika library for Python takes a lot of time to startup a RabbitMQ connection; this means that Zulip server restarts are more disruptive than would be ideal. * It's annoying that you need to run the rabbitmqctl management commands as root.

But overall, I like that it has clean, clear semanstics and high scalability, and haven't been tempted to do the work to migrate to something like Redis (which has its own downsides).

See more
Resque logo

Resque

103
91
9
A Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later
103
91
+ 1
9
CONS OF RESQUE
    No cons available

    related Resque posts

    Beanstalkd logo

    Beanstalkd

    98
    110
    74
    A simple, fast work queue
    98
    110
    + 1
    74

    related Beanstalkd posts

    Frédéric MARAND
    Core Developer at OSInet · | 2 upvotes · 162.1K 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
    Hangfire logo

    Hangfire

    85
    90
    13
    Perform background processing in .NET and .NET Core applications
    85
    90
    + 1
    13
    CONS OF HANGFIRE
      No cons available

      related Hangfire posts

      PHP-FPM logo

      PHP-FPM

      66
      65
      0
      An alternative FastCGI daemon for PHP
      66
      65
      + 1
      0
      PROS OF PHP-FPM
        No pros available
        CONS OF PHP-FPM
          No cons available

          related PHP-FPM posts

          delayed_job logo

          delayed_job

          46
          52
          6
          Database backed asynchronous priority queue -- Extracted from Shopify
          46
          52
          + 1
          6
          CONS OF DELAYED_JOB
            No cons available

            related delayed_job posts

            Jerome Dalbert
            Senior Backend Engineer at StackShare · | 4 upvotes · 69.9K 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 · 44K 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
            Bull logo

            Bull

            38
            70
            4
            Premium Queue package for handling jobs and messages in NodeJS
            38
            70
            + 1
            4

            related Bull posts