Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

beanstalkd

beanstalkd.github.io

  • Free plan
  • macOS
  • Linux
  • Self-hosted

What beanstalkd is

Beanstalkd is a free, self-hosted work queue for running time-consuming tasks asynchronously. Producers place jobs into queues, and worker processes reserve and execute them, helping reduce page-view latency in high-volume web applications. Tubes create separate queues so producers and consumers can operate independently. A reserve command waits until work is available, with a timeout variant also supported. With the -b option, beanstalkd writes jobs to a binlog and can recover them after restart. Jobs may be buried so they stay out of the ready queue until kicked. Clients can use multiple beanstalkd servers, although each server does not know about the others. Listed client libraries cover C, C++, Clojure, Go, Java, JavaScript, Node.js, PHP, Python, Ruby, Rust, and .NET/C#. The project supports the Beanstalk protocol over TCP with ASCII encoding. The source release is MIT-licensed. Listed operating systems include Linux 2.6.17 or later, Mac OS X, FreeBSD, and Illumos.

Who it suits

Beanstalkd suits developers building self-hosted asynchronous job processing, especially for high-volume web applications. It fits teams able to operate queue servers and choose from its listed client libraries.

Good to know, and what to watch

  • Simple producer-and-worker queue model
  • Separate tubes isolate job queues
  • Binlog recovery after restart
  • Jobs can be buried and later kicked
  • Client libraries span many languages
  • Each server lacks awareness of other instances
  • Requires self-hosted operation
  • Listed Linux requirement is 2.6.17 or later
  • No security or compliance claims on official pages

Beanstalk

Free

Free plan

The verdict

Beanstalkd offers a focused queue protocol with persistence, delayed reservation, and broad client-library coverage. Its self-hosted architecture and limited coordination between servers should guide deployment design.

What the maker publishes

Administration
The FAQ points to administration and monitoring tools on the project tools page. source
Architecture
Producers put jobs into the queue and worker processes take jobs out and run them. source
Blocking jobs
The reserve command blocks until a job is available, and reserve-with-timeout is also supported. source
Client integrations
The project lists client libraries for languages including C, C++, Clojure, Go, Java, JavaScript, Node.js, PHP, Python, Ruby, Rust, and .NET/C#. source
Compatibility
The client library page says the 1.x protocol remains compatible until beanstalkd 2.0. source
Distributed setup
Clients can handle multiple beanstalkd servers, but each server does not know about other instances. source
Job handling
Jobs can be buried so they remain out of the ready queue until kicked, which the FAQ says can prevent a timed-out task from being rerun. source
Notable limit
The README lists Linux 2.6.17 or later, Mac OS X, FreeBSD, and Illumos as required operating systems. source
Persistence
With the -b option, beanstalkd writes jobs to a binlog and can recover its contents after restart. source
Purpose
Beanstalk is a simple, fast work queue for running time-consuming tasks asynchronously. source
Queue organization
Tubes are separate job queues that let producers and consumers work independently. source
Security
The project’s download page identifies the source release as MIT-licensed; the opened official pages make no security or compliance claims. source
Support
The site directs bug reports to its mailing list. source
Use case
The site describes reducing page-view latency in high-volume web applications as the queue’s original purpose. source

Checked against the maker's pages on 11 Oct 2026.