no redis · no workers · one binary
A message queue without Redis or Kafka
BullMQ, Sidekiq and Celery need Redis and long-running worker processes. betterMQ bundles storage, scheduling and delivery into one broker that pushes HTTP webhooks instead.
Pull queues vs push queues
Redis + workers (pull)
Workers poll BRPOP, process, ack. You operate Redis HA + worker autoscaling.
betterMQ (push)
Broker POSTs to your URL when ready. Your API is the consumer — scale it like any HTTP service.
What you still get
- · Durable queue with at-least-once delivery
- · Exponential backoff, DLQ, idempotency keys
- · Per-queue rate limits, parallelism and priority 0–9
- · Cron, delays and fan-out groups
- · HMAC-signed webhooks
When Redis queues are still better
Millisecond in-process job latency or millions of tiny jobs/sec — stick with BullMQ or Sidekiq. betterMQ wins when jobs are HTTP-sized tasks across services.