> Everything was Python, except for the queue, which was something implemented on top of Redis.
Could that be... Resque? If so whats the problem mentioning you are using Ruby as well?
Could that be... Resque? If so whats the problem mentioning you are using Ruby as well?
Jobs were originally pushed from our Django app, into a Celery job, which consumed the message, and published into Thoonk. Thoonk was then consumed by the old Python backend.
With this rewrite, we've also removed Thoonk and are using a fanout exchange in Rabbit directly. Go consumes the Celery job from the Rabbit queue.
Just kidding.