3 ms·
I've not much to say other than that this is a great little library! I used RQ for a small project recently and found it to be pretty easy to use. As my project
by sleavey 7y ago
I've not much to say other than that this is a great little library! I used RQ for a small project recently and found it to be pretty easy to use. As my project grew bigger I also found it contained extra features I didn't realise I'd need when I started.
- remlov 7y agoRQ scales surprisingly well and for certain types of projects is a nice lightweight alternative compared to more complicated job queues such as Celery.
- sleavey 7y agoYeah when I was looking at queues I was put off by Celery since somewhere in its docs or a tutorial high up in the Google results it was suggested to use both redis and RabbitMQ as some sort of brokers/results stores rather than just one of those to handle both. I'm sure there were good reasons for that, but I was looking for something simple and not to learn multiple new technologies so in terms of simplicity RQ (which uses redis for everything) is pretty hard to beat.
- disiplus 7y agofor a simple queue the broker is the only important part. i like celery and have projects in multiple languages using rabbitmq.
- mjhea0 7y agoBig fan of this library. I think Celery is overkill for most projects. RQ is nice for the majority projects and it can scale right along with your project. Quick tutorial of Flask + RQ: https://testdriven.io/blog/asynchronous-tasks-with-flask-and-redis-queue/ https://testdriven.io/blog/asynchronous-tasks-with-flask-and...