Show HN: Bunqueue – Job queue for Bun using SQLite instead of Redis(github.com)
github.com
Show HN: Bunqueue – Job queue for Bun using SQLite instead of Redis
https://github.com/egeominotti/bunqueue
22 comments
We are using a service that abstracts redis from us and requires to be treated like a critical dependency, think RDS, Aurora, Postgres, if they are down the whole site is down. Every job push is a call to this service. Upgrading the service = downtime.
For us this is resulted in a big weak point on our architecture because when the service reboots both job pushing and job pulling stops, with the pushing being on the API side bringing the API down. With containers we could have multiple of them running at the same time, but the shared reading/writing of the abstract Redis locks itself.
We are considering BullMQ, because the architecture is sane: * job push: API writes to Redis * job pull: Worker reads from Redis then writes the completion.
How do you see this issue for Bunqueue? What happens when it goes down for 5 minutes, can the jobs be enqueued? Can you run multiple instances of it, failover?
Our throughput (jobs/sec) is small we do have 100k+ scheduled jobs anywhere from minutes to months from now.
For us this is resulted in a big weak point on our architecture because when the service reboots both job pushing and job pulling stops, with the pushing being on the API side bringing the API down. With containers we could have multiple of them running at the same time, but the shared reading/writing of the abstract Redis locks itself.
We are considering BullMQ, because the architecture is sane: * job push: API writes to Redis * job pull: Worker reads from Redis then writes the completion.
How do you see this issue for Bunqueue? What happens when it goes down for 5 minutes, can the jobs be enqueued? Can you run multiple instances of it, failover?
Our throughput (jobs/sec) is small we do have 100k+ scheduled jobs anywhere from minutes to months from now.
Transparent answer about bunqueue's architecture.
Current state: bunqueue is single-server with SQLite persistence.
If the server goes down for 5 minutes, clients cannot push/pull during that window. However: the client SDK has automatic reconnection with exponential backoff + jitter, all data is safe on disk (SQLite WAL mode), and on restart active jobs are detected as stalled and re-queued automatically. Delayed/scheduled jobs resume from their run_at timestamps.
For your use case (100k+ scheduled jobs, low throughput): well-optimized. We use MinHeap + SQLite indexes for O(k) refresh where k = jobs becoming ready, not O(n) scan.
What bunqueue does NOT have today: no clustering, no multi-instance with shared state, no automatic failover, no replication.
What it does have: S3 automated backups (compressed, checksummed) for disaster recovery. A "durable: true" option for zero data loss on critical jobs. Zero external dependencies.
Roadmap: HA is something we're actively working toward. Native HA with leader election and replication. Managed cloud offering with automatic failover and geographic distribution.
Bottom line: if you need true HA today, BullMQ + Redis Sentinel/Cluster is the safer choice. bunqueue is for when you want simplicity, high performance (~100k jobs/sec), and can tolerate brief downtime with automatic recovery.
Current state: bunqueue is single-server with SQLite persistence.
If the server goes down for 5 minutes, clients cannot push/pull during that window. However: the client SDK has automatic reconnection with exponential backoff + jitter, all data is safe on disk (SQLite WAL mode), and on restart active jobs are detected as stalled and re-queued automatically. Delayed/scheduled jobs resume from their run_at timestamps.
For your use case (100k+ scheduled jobs, low throughput): well-optimized. We use MinHeap + SQLite indexes for O(k) refresh where k = jobs becoming ready, not O(n) scan.
What bunqueue does NOT have today: no clustering, no multi-instance with shared state, no automatic failover, no replication.
What it does have: S3 automated backups (compressed, checksummed) for disaster recovery. A "durable: true" option for zero data loss on critical jobs. Zero external dependencies.
Roadmap: HA is something we're actively working toward. Native HA with leader election and replication. Managed cloud offering with automatic failover and geographic distribution.
Bottom line: if you need true HA today, BullMQ + Redis Sentinel/Cluster is the safer choice. bunqueue is for when you want simplicity, high performance (~100k jobs/sec), and can tolerate brief downtime with automatic recovery.
Thank you for your detailed reply! Appreciated it
> Best for single server or small clusters
How would this work for anything _but_ a single server?
How would this work for anything _but_ a single server?
Fair point, that was misleading. bunqueue is single-server only today. “Small clusters” is on the roadmap but I should’ve been clearer it’s not there yet.
At Apple, on iTunes, we used an Oracle database to do job queue stuff. Initially I will admit I made fun of it because I wanted to use a "real" queue like RabbitMQ or ActiveMQ or something, but I have to admit that it worked fine and to be fair it did predate both of those.
Anyway, it made me realize that there's really no reason you can't use a SQL database as a backing store for queue stuff. I should try building my own at some point.
Anyway, it made me realize that there's really no reason you can't use a SQL database as a backing store for queue stuff. I should try building my own at some point.
This is exactly why I built bunqueue — a job queue for Bun backed by SQLite. No Redis, no external dependencies, just bun:sqlite with WAL mode for concurrent access. Handles 100k+ jobs/sec on a single node.
The SQL-as-queue pattern is definitely underrated. Great to hear it worked well at that scale.
The SQL-as-queue pattern is definitely underrated. Great to hear it worked well at that scale.
> This is exactly why I built bunqueue — a job queue for Bun backed by SQLite. No Redis, no external dependencies, just bun:sqlite with WAL mode for concurrent access. Handles 100k+ jobs/sec on a single node.
If you're too lazy to even write your own comments, I suspect you're too lazy to have written your own software.
At least preface your comment with "The LLM says" or preface your submission with "The LLM wrote this software".
If you're too lazy to even write your own comments, I suspect you're too lazy to have written your own software.
At least preface your comment with "The LLM says" or preface your submission with "The LLM wrote this software".
To be honest I don't see anything egregious here.
Why do you think that was written with a LLM?
The comment sounds "polished" because I've probably described this project dozens of times at this point.
When you repeat the same thing over and over you naturally end up with a tight version of it. That's not an LLM, that's just how it works when you talk about something a lot.
And honestly even if I did use an LLM to write a comment on HN, so what? The code is what matters.
Go run the benchmarks, read the source, open an issue if something breaks.
That's the part that actually counts.
When you repeat the same thing over and over you naturally end up with a tight version of it. That's not an LLM, that's just how it works when you talk about something a lot.
And honestly even if I did use an LLM to write a comment on HN, so what? The code is what matters.
Go run the benchmarks, read the source, open an issue if something breaks.
That's the part that actually counts.
> The comment sounds "polished" because I've probably described this project dozens of times at this point.
I didn't say it sounded "polished", I said exactly the opposite.
> And honestly even if I did use an LLM to write a comment on HN, so what?
If we wanted to chat with bots, we know where to find them.
I didn't say it sounded "polished", I said exactly the opposite.
> And honestly even if I did use an LLM to write a comment on HN, so what?
If we wanted to chat with bots, we know where to find them.
> And honestly even if I did use an LLM to write a comment on HN, so what? The code is what matters.
Part of what makes these forums fun is human responses. LLMs write "good enough" text but they come off as robotic and inhuman. The only reason to go onto one of these forums is to communicate with people. If I wanted to talk to a robot, I would talk to ChatGPT, which I can do as often as I want.
Part of what makes these forums fun is human responses. LLMs write "good enough" text but they come off as robotic and inhuman. The only reason to go onto one of these forums is to communicate with people. If I wanted to talk to a robot, I would talk to ChatGPT, which I can do as often as I want.
I get the concern, but there’s a spectrum.
Using an LLM to polish grammar vs. having it generate opinions wholesale are different things.
Using an LLM to polish grammar vs. having it generate opinions wholesale are different things.
I'm not necessarily saying that you used an LLM, but em dashes aren't used that often when regular people are typing. I use Grammarly all the time and they've never suggested that I add an em dash, and it's often a sign of a low-effort "ask ChatGPT for a response to this comment".
Again, not necessarily saying that's what you did, just that that's the red flag.
Again, not necessarily saying that's what you did, just that that's the red flag.
I remember in my early dev days thinking I was clever for creating a queue. Was right in MySQL handing forum posts back when building your own forum software was a normal thing. It worked fine. Was it optimal? Not really but neither was the entire app. Didn’t matter at the time and probably doesn’t matter today either for most apps.
True, most apps will never hit the scale where it matters. But when you do, retrofitting a queue is painful.
The idea: for single-server deployments, SQLite can handle 100k+ ops/sec with WAL mode, so why add infrastructure?
Features: priorities, delays, retries, cron jobs, DLQ, job dependencies, BullMQ-compatible API.