The idea: for single-server deployments, SQLite can handle 100k+ ops/sec with WAL mode, so why add infrastructure?
Two modes: - Embedded: everything in-process, just `import` and go - Server: run `bunqueue start`, connect multiple workers via TCP
Trade-offs vs Redis: - Not for multi-region distributed systems - Best for single server or small clusters Happy to answer any questions about the architecture!
kernelvoid•1h ago
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.