Proposal) Reply-To:
On Mon, May 09, 2016 at 01:49:26PM -0600, Kevin Fenzi wrote:
We have tried to avoid celery serveral times in the past and always managed to, but perhaps we can't this time. Is there any alternative to the celery use?
Outside of the topic at hand, do you remember the reasons why we tried to avoid celery until now?
Was this something specific to celery? Or AMQP in general? Or?
Since I'm investigating changing the architecture of FMN's backend in such a way that it would use both redis and AMQP (rabbitmq to be precise), I'm curious if there is anything I should be aware of before going to far down this road :)
Thanks, Pierre
On Wed, 11 May 2016 22:59:44 +0200 Pierre-Yves Chibon pingou@pingoured.fr wrote:
Proposal) Reply-To:
On Mon, May 09, 2016 at 01:49:26PM -0600, Kevin Fenzi wrote:
We have tried to avoid celery serveral times in the past and always managed to, but perhaps we can't this time. Is there any alternative to the celery use?
Outside of the topic at hand, do you remember the reasons why we tried to avoid celery until now?
Was this something specific to celery? Or AMQP in general? Or?
I think it was related to askbot... it wanted to use celery, but only to handle email sending or something, which seemed like way overkill.
There may have been some other app that wanted it, but I can't seem to think of it off hand. ;(
Since I'm investigating changing the architecture of FMN's backend in such a way that it would use both redis and AMQP (rabbitmq to be precise), I'm curious if there is anything I should be aware of before going to far down this road :)
It was just a matter of running another big service for something that didn't need it. Perhaps it makes sense for FMN.
kevin
infrastructure@lists.fedoraproject.org
-
Kevin Fenzi -
Pierre-Yves Chibon