Hi Régis, I'm on a different team at edX, but I can give a little more context on RabbitMQ. We've had a lot of operational issues with RabbitMQ under load and have found Redis to be better behaved. The fact that AWS offers a managed version of it is also very appealing. From a code point of view though, we're still committed to using interface libraries like Celery and Kombu to abstract the specific broker away, so Open edX installs should have the flexibility to continue with RabbitMQ if that works well for them.
Take care. Dave On Wed, Jan 17, 2018 at 3:57 AM, Régis Behmo <[email protected]> wrote: > Hi Sandy, > > > as we move away from using RabbitMQ > > Could you give a bit more background on this? How do you intend to replace > RabbitMQ for running asynchronous celery tasks? > > Régis > > -- > You received this message because you are subscribed to the Google Groups > "General Open edX discussion" group. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/edx-code/14bd2c49-f8fa-48ef-b225-f530c772568d%40googlegroups.com > <https://groups.google.com/d/msgid/edx-code/14bd2c49-f8fa-48ef-b225-f530c772568d%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "General Open edX discussion" group. To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/CAO_oFPwJMgJ_PDjn%3DR_BL%2BQeU4Fs%3DRUkpmwTBULpOnN0vR4zFw%40mail.gmail.com.
