Hello, The answer probably depends on what we want to do with Rabbit MQ. What protocol do we intend to support and for what use cases ? Supporting a lot of protocol is not feasible IMO considering the size of our team.
IMO we should concentrate our efforts on: - HTTP/2 - IOT protocol (MQTT or something else) I didn't dig but few questions we need to tackle: - Are RabbitMQ plugins available on client side for MQTT, Stomp ? - Are they all licensed in ASL2 ? or only some of them ? Regards On Fri, Dec 30, 2016 at 11:33 AM, Antonio Gomes Rodrigues <[email protected]> wrote: > Hi all, > > I am thinking about adding support for more messaging protocols > (AMQP/MQTT/Stomp/...) > To do it, we have 2 choices : > Use ActiveMQ Java client > Use RabbitMQ Java client > > I have checked some plugin to JMeter and Gatling and all use RabbitMQ Java > client. > > ActiveMQ is compatible with only AMQP 1.0 whereas RabbitMQ is compatible > with AMQP 0.9 (and 1.0 with a plugin). AMQP 1.0 is not compatible with AMQP > 0.9, but I do not know if there is an impact on client side > > I propose to use RabbitMQ Java client ( > https://www.rabbitmq.com/java-client.html). > The license seems OK > > "The library is open-source, and is triple-licensed under > Apache Public License 2.0 > Mozilla Public License > GPL 2.0" > > If anybody have a better idea, please share it > > Plugins: > https://github.com/maiha/gatling-amqp > https://github.com/fhalim/gatling-rabbitmq > https://github.com/jlavallee/JMeter-Rabbit-AMQP > > Thanks, > Antonio > -- Cordialement. Philippe Mouawad.
