Flask-RQ2
A Flask extension for RQ. (by rq)
flower
Real-time monitor and web admin for Celery distributed task queue (by mher)
| Flask-RQ2 | flower | |
|---|---|---|
| 3 | 3 | |
| 224 | 6,169 | |
| 0.9% | - | |
| 0.0 | 7.7 | |
| 7 days ago | 14 days ago | |
| Python | Python | |
| MIT License | BSD 3-clause "New" or "Revised" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
Flask-RQ2
Posts with mentions or reviews of Flask-RQ2.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-12.
-
Wondering if I should use Celery vs threads for what I want to do
From experience i would not use threads for this or any background jobs. I would use Celery or Flask-RQ2 to be your workers, you will also probably end up using them to run other tasks as you encounter the need for other jobs. They both use Redis as a broker and job store and you can use Redis for other things like caching and so many other useful features. I kind of like RQ2 more then Celery because its a little simpler but Celery has a lot more to offer, more features. RQ2 has rq-dashboard for monitoring jobs and Celery has Flower.
-
Tutorials on how to build a flask extension?
However, you might need to access the app’s context like how you’d do so in the Flask-RQ2 extension by using ScriptInfo from flask.cli:
-
Application structure for CLI and API in same
For the CLI part, i recommend going with Click. Its great and already part of flask and easy to use. Other CLI libraries work too but why have more libraries. For scheduling jobs you might want to look at Flask-APScheduler. i used it in one of my projects at work for a while but ended up needing something that could scale to many more workers so had to rip it out but i didnt have a problem with it otherwise. You might want to fork Flask-APScheduler so you can update some libraries because it hasnt been touched in 2 years now or you can just use APScheduler alone. Flask-RQ2 and Celery are pretty good too but the workers need to run in separate processes and need Redis. You could use Redislite i think and with celery you could use a database as your broker, i have done it but dont recommend it.
flower
Posts with mentions or reviews of flower.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-04.
-
Scaling Celery to handle workflows and multiple queues
Use flower to monitor workers and tasks.
-
Python Celery - high level overview(animated video)
Not sure what your criteria for good observability ist, but flower served me well enough for this in the last couple of years.
-
Wondering if I should use Celery vs threads for what I want to do
From experience i would not use threads for this or any background jobs. I would use Celery or Flask-RQ2 to be your workers, you will also probably end up using them to run other tasks as you encounter the need for other jobs. They both use Redis as a broker and job store and you can use Redis for other things like caching and so many other useful features. I kind of like RQ2 more then Celery because its a little simpler but Celery has a lot more to offer, more features. RQ2 has rq-dashboard for monitoring jobs and Celery has Flower.
What are some alternatives?
When comparing Flask-RQ2 and flower you can also consider the following projects:
rq - Simple job queues for Python
django-suit - Modern theme for Django admin interface
rq-scheduler - A lightweight library that adds job scheduling capabilities to RQ (Redis Queue)
django-jet - Modern responsive template for the Django admin interface with improved functionality. We are proud to announce completely new Jet. Please check out Live Demo
rq-dashboard - Flask-based web front-end for monitoring RQ queues
Celery-Kubernetes-Operator - An operator to manage celery clusters on Kubernetes (Work in Progress)
flask-apscheduler - Adds APScheduler support to Flask
flask-admin - Simple and extensible administrative interface framework for Flask
arq - Fast job queuing and RPC in python with asyncio and redis.
django-todo - A multi-user, multi-group todo/ticketing system for Django projects. Includes CSV import and integrated mail tracking.
django-celery-results - Celery result back end with django