django-rq
rq
django-rq | rq | |
---|---|---|
15 | 27 | |
1,766 | 9,518 | |
0.7% | 0.7% | |
7.1 | 8.3 | |
5 days ago | 11 days ago | |
Python | Python | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
django-rq
-
Background jobs with Django
For simple stuff, I tend to use https://github.com/rq/django-rq. Although scheduling tasks there does not work well in my experience. If I need something to run by schedule, than better just plain cron.
- Keep the Monolith, but Split the Workloads
-
django-rq VS django-q2 - a user suggested alternative
2 projects | 21 Mar 2023
-
How We Built an Application to Test Student Docker Images for Database Systems University Course
Performing tests on student images can be a time-consuming process, taking several minutes. Application has to download the image from the registry, create a container, wait for the application to load, and perform the test scenarios. To efficiently utilize the available hardware and handle increased server demand during peak times, a task queue was implemented using django-rq.
-
Recommendations other than celery to send an API processing in background, which would only take 5 mins to process and API usage would be once a month or so.
Yep, rq is simple and good: https://python-rq.org/ It also has a Django wrapper: https://github.com/rq/django-rq
-
Alternative for Django Celery.
I use RQ (Redis Queue) and it's very cool! https://github.com/rq/django-rq https://python-rq.org/patterns/django/
-
Show HN: Chard – simple async/await background tasks for Django
I love the simplicity of this idea because for lots of sites the database works just fine as a queue backend and it reduces the amount of infrastructure needed. I currently use https://github.com/dabapps/django-db-queue for devmarks.io which also uses the database to store tasks instead of a dedicated queue infrastructure. `Django Q` also has an option to use the database, but I haven't tested it at all: https://django-q.readthedocs.io/en/latest/configure.html#orm. And if you are already running `redis` for your site, https://github.com/rq/django-rq is another option.
The one benefit of this package is that it is async-first which will be beneficial as Django continually adds in more async capabilities. Nice work! I'm looking forward to trying this out and seeing how it works!
-
Simple Task Queue system that works with Django 4 / Python 3.9?
https://github.com/rq/django-rq if you already have redis available or https://github.com/dabapps/django-db-queue for something even simpler. I’ve used both and vastly prefer them over celery.
-
Celery Alternative for Django - Huey | Idiomatic Programmers
if you use redis there is https://github.com/rq/django-rq as well
- How do you guys automate emails with django?
rq
-
Redis Re-Implemented with SQLite
That's pretty cool. Reckon it would work with existing code that calls Redis over the wire for RQ?
https://python-rq.org
-
The Many Problems with Celery
https://github.com/rq/rq is to the rescue.
-
Keep the Monolith, but Split the Workloads
We use RQ[0], it has Redis as a dependency. It’s pretty straightforward and we’re very happy with it. If you are using Django you may want to look at Django RQ[1] as well. RQ has built in scheduling capabilities these days, but historically it did not so we used (and still use) RQ Scheduler[2] which I think still has some advantages over the built in stuff.
[0] https://python-rq.org/
-
SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a Postgres Queue
Also had a similar experience using RabbitMQ with Django+Celery. Extremely complicated and workers/queues would just stop for no reason.
Moved to Python-RQ [1] + Redis and been rock solid for years now.
[1] https://python-rq.org/
- Ask HN: Redis Queue Hacks and Questions
- What libraries do you use the most alongside django?
-
Recommendations other than celery to send an API processing in background, which would only take 5 mins to process and API usage would be once a month or so.
Yep, rq is simple and good: https://python-rq.org/ It also has a Django wrapper: https://github.com/rq/django-rq
-
GPU instance crashes when two python processes use the same pt file
We have a GPU (G5) instance that uses Python RQ (https://python-rq.org/).
- Dynamically update periodic tasks in Celery and Django
- Celery + RabbitMQ alternatives
What are some alternatives?
celery - Distributed Task Queue (development branch)
rq-scheduler - A lightweight library that adds job scheduling capabilities to RQ (Redis Queue)
huey - a little task queue for python
django-q - A multiprocessing distributed task queue for Django
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
django-background-tasks - A database-backed work queue for Django
mrq - Mr. Queue - A distributed worker task queue in Python using Redis & gevent
django-q2 - A multiprocessing distributed task queue for Django. Django Q2 is a fork of Django Q. Big thanks to Ilan Steemers for starting this project. Unfortunately, development has stalled since June 2021. Django Q2 is the new updated version of Django Q, with dependencies updates, docs updates and several bug fixes. Original repository: https://github.com/Koed00/django-q
procrastinate - PostgreSQL-based Task Queue for Python
packwerk - Good things come in small packages.
Apache Kafka - Mirror of Apache Kafka