Beanstalkd vs delayed_job: What are the differences?
What is Beanstalkd? A simple, fast work queue. 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.
What is delayed_job? Database backed asynchronous priority queue -- Extracted from Shopify. 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.
Beanstalkd and delayed_job can be primarily classified as "Background Processing" tools.
"Fast" is the primary reason why developers consider Beanstalkd over the competitors, whereas "Easy to get started" was stated as the key factor in picking delayed_job.
Beanstalkd and delayedjob are both open source tools. It seems that Beanstalkd with 5.12K GitHub stars and 748 forks on GitHub has more adoption than delayedjob with 4.46K GitHub stars and 915 GitHub forks.
According to the StackShare community, Beanstalkd has a broader approval, being mentioned in 27 company stacks & 8 developers stacks; compared to delayed_job, which is listed in 8 company stacks and 5 developer stacks.
What is Beanstalkd?
What is delayed_job?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Beanstalkd?
What are the cons of using delayed_job?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Beanstalkd?
What tools integrate with delayed_job?
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.
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!