Home
Application and Data
Data Stores
Background Processing

Faktory vs Resque

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

Faktory
6
27
+ 1
3
Resque
118
124
+ 1
9
Add tool

Faktory vs Resque: What are the differences?

Faktory: Background jobs for any language, by the makers of Sidekiq. 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; Resque: A Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later. 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.

Faktory and Resque can be categorized as "Background Processing" tools.

Faktory and Resque are both open source tools. It seems that Resque with 8.54K GitHub stars and 1.57K forks on GitHub has more adoption than Faktory with 3.41K GitHub stars and 136 GitHub forks.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Faktory
Pros of Resque
  • 2
    Worker language agnostic
  • 1
    Simple service API
  • 5
    Free
  • 3
    Scalable
  • 1
    Easy to use on heroku

Sign up to add or upvote prosMake informed product decisions

What is Faktory?

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.

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

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

What companies use Faktory?
What companies use Resque?
See which teams inside your own company are using Faktory or Resque.
Sign up for StackShare EnterpriseLearn More

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

What tools integrate with Faktory?
What tools integrate with Resque?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Faktory and Resque?
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 gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
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.
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
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.
See all alternatives

Related Comparisons

Que vs Resque vs SidekiqResque vs Sidekiq vs delayed_jobKue vs ResqueBeanstalkd vs Resque vs SidekiqFaktory vs Sidekiq

Trending Comparisons

Django vs Laravel vs Node.jsBootstrap vs Foundation vs Material-UINode.js vs Spring BootFlyway vs LiquibaseAWS CodeCommit vs Bitbucket vs GitHub

Top Comparisons

Bootstrap vs MaterializeBitbucket vs GitHub vs GitLabPostman vs Swagger UIHipChat vs Mattermost vs Slack