4 ms·
we used it to replace rabbitmq for our django->celery communication. rabbitmq had given us some configuration challenges, while redis just dropped in and worked
by robertfw 13y ago
we used it to replace rabbitmq for our django->celery communication. rabbitmq had given us some configuration challenges, while redis just dropped in and worked out of the box.
- erichurkman 13y agoOne nice thing, too, is that you can keep the celery queue on a separate redis database in the same instance(s) -- to keep it separate from your other cache data. I like to keep my databases separate -- one for task queues, another for sessions, and another for truly persistent data. This makes some workflows very easy, like needing to invalidate all sessions or needing to purge transient cache data after deploying new code. Simply flush those databases.