mrq vs sidequest
Distributed background job queues compared
mrq and sidequest both run background jobs across workers and provide tools for scheduling and monitoring. mrq is a Python queue built around Redis, MongoDB, and gevent, while sidequest is a Node.js processor that stores jobs in a supported database without requiring Redis.

mrq: Distributed Python Task Queue on Redis and gevent
MRQ is a distributed Python task queue built on MongoDB, Redis, and gevent, designed to handle mixed I/O-bound and CPU-bound jobs. It offers queue management, scheduling, workers, and a dashboard, but has seen no recent maintenance.

sidequest: Run Durable Node.js Background Jobs Without Redis
Sidequest is a Redis-free background job processor for Node.js that stores durable jobs in PostgreSQL, MySQL, SQLite, or MongoDB. It offers distributed processing, scheduling, retries, and a built-in dashboard for teams that want to use their existing database.
| mrq | sidequest | |
|---|---|---|
| Language | Python | TypeScript |
| License | MIT | LGPL-3.0 |
| Stars | 892 | 1k |
| Forks | 115 | 30 |
| Last analyzed | Oct 29, 2026 | Oct 28, 2026 |
Key differences
- mrq targets Python applications and uses Redis and MongoDB; sidequest targets Node.js and supports PostgreSQL, MySQL, SQLite, or MongoDB storage.
- mrq uses gevent for concurrent I/O work and can scale CPU-bound work across UNIX processes; sidequest uses worker threads by default and also offers inline and no-fork modes.
- mrq offers sequential, parallel, and burst dequeue strategies; sidequest includes job uniqueness controls and automatic stale-job recovery.
- mrq is licensed under MIT; sidequest is licensed under LGPL-3.0-or-later.
- mrq's latest recorded push was in 2023, so teams are advised to check its current compatibility and maintenance status; sidequest requires Node.js 22.6.0 or later and has 18 open issues to review.
Choose mrq if you…
- need a Python task queue with Redis and MongoDB backing job and queue data.
- want gevent concurrency for I/O-bound work and process-based scaling for CPU-bound jobs.
- need a dashboard for worker visibility, job logs, and job management.
Choose sidequest if you…
- want Node.js background jobs stored in a supported database without adding Redis.
- need workers to coordinate across nodes through a shared database.
- want features such as cron scheduling, configurable retries, and job uniqueness controls.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.