RQ is simple, stable and reliable. Redis is also a persistent storage, but
you should read about this and use the best solution for your case:
https://redis.io/topics/persistence
You may also consider deploying a fault-tolerant Redis cluster (min. 3
nodes AFAIR)
RQ has different
try googling 'python task queue'
see https://www.fullstackpython.com/task-queues.html
On Thu, Apr 20, 2017 at 12:25 PM, Andréas Kühne
wrote:
> I don't know anything about the python-rq stuff - however redis can be
> configured to save to disk (see
I don't know anything about the python-rq stuff - however redis can be
configured to save to disk (see https://redis.io/topics/persistence) - so
you wouldn't loose anything on a power-failure (if configured correctly).
Redis is so much more than a cache nowadays.
Regards,
Andréas
2017-04-20
Some years ago I used celery for a project.
Today I face roughly the same use case again.
The last time I used it, celery felt to heavy weighted, too complicated.
I found this alternative: http://python-rq.org/
There are two things which speak agains python-rq:
- redis is a cache. I need a
4 matches
Mail list logo