rq-scheduler
django-rq
Our great sponsors
rq-scheduler | django-rq | |
---|---|---|
4 | 15 | |
1,384 | 1,760 | |
0.9% | 1.3% | |
2.2 | 7.0 | |
about 1 month ago | 5 days ago | |
Python | Python | |
MIT License | MIT License |
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.
rq-scheduler
- Keep the Monolith, but Split the Workloads
-
RQ-Scheduler for tasks in far future?
RQ-Scheduler is another simpler alternative (rq/rq-scheduler: A lightweight library that adds job scheduling capabilities to RQ (Redis Queue) (github.com)) that appears to be good for such purposes. It's not immediately clear if it would suffer from the same issues, but it seems not (Redis manages issues with data loss well, a separate queue is used for the scheduled tasks, etc.). Is anyone aware of any drawbacks to using RQ-Scheduler for something like this?
- Need direction on how to add asynchronous / scheduled tasks on my flask app running on aws beanstalk
-
Some advice: will my setup be production ready?
Some thoughts: - Storing API keys in Redis with AOF and RDB persistence turned on is going to be way faster than storing those keys in Mongo. - Did you mean RQ (redis-queue)/django-rq? If so, it works well as long as you don't need a scheduler for cron-like tasks, which it doesn't include. You can add rq-scheduler for that though: https://github.com/rq/rq-scheduler - Make sure your redis instance has a password -- redis 6 supports ACLs as well - The problem with slow requests is that they tie up app server processes and usually also database connections. That may be fine with a small number of consumers, but if you point your web site at this API, you may run into problems. Consider that if an app server serving web site traffic is waiting for a slow request to your API, then both app servers are affected -- you're now holding resources on the web site and the API, effectively. - HTTP clients often use a default timeout value for requests, and it's a best practice to use such a timeout -- so you'll need to coach your partners consuming this API not to use timeouts for your API.
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?
What are some alternatives?
fastapi-cloud-tasks - GCP's Cloud Tasks + Cloud Scheduler + FastAPI = Partial replacement for celery.
celery - Distributed Task Queue (development branch)
rq - Simple job queues for Python
Flask-RQ2 - A Flask extension for RQ.
django-q - A multiprocessing distributed task queue for Django
django-rq - A simple app that provides django integration for RQ (Redis Queue) [Moved to: https://github.com/rq/django-rq]
django-background-tasks - A database-backed work queue for Django
supervisor - Supervisor process control system for Unix (supervisord)
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
NiceHash-Mining-Scheduler - Schedule the start and stop of your NiceHash miners using this script.
packwerk - Good things come in small packages.