What is 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.
delayed_job is a tool in the Background Processing category of a tech stack.
delayed_job is an open source tool with 4.8K GitHub stars and 960 GitHub forks. Here’s a link to delayed_job's open source repository on GitHub
Who uses delayed_job?
13 companies reportedly use delayed_job in their tech stacks, including gemini, feedforce Inc., and Open Food Network UK.
37 developers on StackShare have stated that they use delayed_job.
Pros of delayed_job
Easy to get started
Doesn't require Redis
delayed_job Alternatives & Comparisons
What are some alternatives to delayed_job?
See all alternatives
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 gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
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.
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.
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.