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 architecture than Celery. It is based on fork(), which is just slower. So you should ask yourself how many tasks per sec you need to handle. RQ may not be enough for all use cases. Some things aren't OOTB, like repeating failed tasks (you should handle it manually, i.e. by using own worker class), nor tasks scheduling (you should use rq-scheduler). RQ uses pickle, but there is a feature request about handling json and other serializers - https://github.com/nvie/rq/issues/369 -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/d2fc1e0f-f147-4ccd-991f-1b12e61c8964%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
