procrastinate
rq-scheduler
Our great sponsors
procrastinate | rq-scheduler | |
---|---|---|
7 | 4 | |
735 | 1,386 | |
4.6% | 1.1% | |
9.6 | 2.2 | |
5 days ago | about 2 months 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.
procrastinate
-
Running Procrastinate from command line throwing exception
I did find this PR which adds a much more detailed description of what to do, although some of it is a bit outdated.
- Anything can be a message queue if you use it wrongly enough
-
The Many Problems with Celery
What about https://github.com/procrastinate-org/procrastinate (postgresql task queue with transactions & stuff)
-
Keep the Monolith, but Split the Workloads
If you're using PostgreSQL, then
django-postgres-queue: https://github.com/gavinwahl/django-postgres-queue
procrastinate: https://github.com/procrastinate-org/procrastinate/
-
Issues/Experience with Procrastinate library for distributed tasks
We chose the Procrastinate library to run periodic tasks.
- Alchemical Queues: (task) queues on pure SQLAlchemy
- Grafana releases OnCall open source project
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.
What are some alternatives?
rq - Simple job queues for Python
fastapi-cloud-tasks - GCP's Cloud Tasks + Cloud Scheduler + FastAPI = Partial replacement for celery.
KQ - Kafka-based Job Queue for Python
django-rq - A simple app that provides django integration for RQ (Redis Queue)
rele - Easy to use Google Pub/Sub
celery - Distributed Task Queue (development branch)
huey - a little task queue for python
Flask-RQ2 - A Flask extension for RQ.
Streamz - Real-time stream processing for python
django-rq - A simple app that provides django integration for RQ (Redis Queue) [Moved to: https://github.com/rq/django-rq]
kombu - Messaging library for Python.
supervisor - Supervisor process control system for Unix (supervisord)