Open 13rac1 opened 9 years ago
Spoke with Halsey about this a little. Celery required RabbitMQ or Redis as a broker. There is another ticket (#83 now closed) that mentions replacing D-Bus with RabbitMQ. There are two considerations I would like thoughts on 1) Is it worth implementing celery now to close this bug without touching D-Bus, or should they be tackled simultaneously? 2) Celery has stable support for RabbitMQ or Redis. Issue #83 lists ZeroMQ or ActiveMQ as other options. Would it make sense to centralize on a broker that supports both Celery and replacing D-Bus.
Outgoing notification emails are currently handled in synchronously during object add/edit/delete. This significantly slows down API/Admin response times. Email and other long running processes should be handled in a task/cron queue.
Here's Celery: http://www.celeryproject.org/