Hacker News Reader

We would probably use this tomorrow (replacing self managed Rabbit MQ instances) if celery/kombu supported ActiveMQ. Might be the service that generates the volunteers needed to add ActiveMQ support to Kombu. (Not ruling out attempting this myself either).

View on HN

> With Amazon MQ support standard protocols for messaging, including JMS, NMS, AMQP, STOMP, MQTT, and WebSocket. This allows you to move from any message broker that uses these standards to Amazon MQ–along with the supported applications–without rewriting code.

Celery/kombu speaks AMQP, which is natively supported by AmazonMQ, so you might be able to move to it with no changes to your app.

You sure that's AMQP 1.0 or 0.9? I say that b/c ActiveMQ is AMQP 1.0 (http://activemq.apache.org/amqp.html) and RabbitMQ is probably running 0.9 unless you are using the experimental 1.0 plugin.

Nearly all the libraries working with AMQP 0.9 will not function when targeting an AMQP 1.0 service.

Maybe, I'll probably try to spin up an instance and test it. But the celery docs call out explicit lack of support for STOMP and ActiveMQ here http://docs.celeryproject.org/en/latest/faq.html#can-i-use-c...

Reply on news.ycombinator.com