dramatiq vs mrq
Python background task queues compared
dramatiq and mrq both let Python applications queue work for separate workers. dramatiq focuses on actor-based task processing with RabbitMQ or Redis, while mrq combines Redis and MongoDB with worker visibility, job controls, and scheduling features.

dramatiq: Run Background Tasks in Python
Dramatiq is a Python library for distributing background jobs through RabbitMQ or Redis. It suits Python services that need workers to process tasks outside the request path, with an active project and an LGPL license to review.

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.
| dramatiq | mrq | |
|---|---|---|
| Language | Python | Python |
| License | LGPL-3.0 | MIT |
| Stars | 5.3k | 892 |
| Forks | 385 | 115 |
| Last analyzed | Oct 14, 2026 | Oct 29, 2026 |
Key differences
- dramatiq defines tasks as actors and enqueues them with `.send()`; mrq offers queue jobs, multiple dequeue strategies, and scheduling by interval or time of day.
- dramatiq supports RabbitMQ or Redis; mrq requires both Redis and MongoDB.
- mrq provides a dashboard for job and worker status, logs, and job management; dramatiq's listed features focus on defining, enqueueing, and processing actor work.
- mrq uses gevent for concurrent I/O-bound jobs and can scale CPU-bound work across UNIX processes with Supervisord integration; dramatiq distributes execution across worker processes.
- dramatiq is licensed under LGPL-3.0, while mrq is licensed under MIT.
- dramatiq has 5.3k stars and 385 forks; mrq has 892 stars and 115 forks, and its latest recorded push was in 2023.
Choose dramatiq if you…
- need actor-based task processing in a Python application.
- already use RabbitMQ or Redis and want to use that broker for background tasks.
- want to distribute jobs across worker processes without the listed dashboard and job-management features.
Choose mrq if you…
- need a dashboard to inspect jobs, workers, and per-job logs, and to manage jobs.
- want gevent concurrency for I/O-bound work and process-based scaling for CPU-bound work.
- need scheduling, routing, timeouts, TTLs, or multiple dequeue strategies.
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.