Beanstalkd

Beanstalkd — simple, fast work queue with tubes and priorities.

QueueSimple

Stack Components

Serverbeanstalkd 1.x

Why

Tiny, fast, persistent, simple protocol, great for job queues. Kafka processes 7 trillion+ messages/day at LinkedIn.

Redis Streams and BullMQ offer simpler queueing for Node.js apps, handling 100k+ jobs/sec on a single instance.

When

Use for background job queues. Avoid for complex routing.

How

1. Run beanstalkd 2. Connect with client library 3. Put/reserve jobs 4. Use tubes for separation 5. Add environment configuration — cp .env.example .env && edit values 6. Run tests — npm test or pnpm test to verify setup 7. Deploy — git push to trigger CI/CD or manual deploy

Example

const beanstalkd = require('fivebeans'); const client = new beanstalkd.Client({ host: '127.0.0.1', port: 11300 }); client.put('default', 0, 0, 60, JSON.stringify(job), () => {});

Common Problems

⚠No clustering — use for single-node
⚠Job loss on crash — enable binlog
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use TTR for job timeouts
✓Bury failed jobs for inspection
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is Beanstalkd and what projects is it for?

Beanstalkd — simple, fast work queue with tubes and priorities. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with Beanstalkd in 10 minutes?

Two steps: (1) Run beanstalkd; (2) Connect with client library. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with Beanstalkd and how do I avoid it?

The most common pitfall is: No clustering — use for single-node. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for Beanstalkd?

Best practices for Beanstalkd include: Use TTR for job timeouts; Bury failed jobs for inspection; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use TTR for job timeouts" — should be set up at project init to avoid costly rework later.

When should I NOT choose Beanstalkd?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). Beanstalkd shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.