I think you are confusing wire-based vs. API-based messaging. ActiveMQ is API-based messaging where API is Java Messaging Service (JMS) hence restrictions to both sides (producer/consumer) + broker being Java-based (although it doesn't have to be in theory). Kafka, AMQP and others are wire-based which essentially means there is a runtime independent protocol for communication allowing Java and non-Java clients to exchange messages.
Kafka does not implement JMS, nor it ever will (I hope) as it would be a step backwards limiting Kafka to only JVM-based clients. Hopefully, this helps to eliminate the confusion. Cheers Oleg > On May 9, 2016, at 20:49, Varun Sood <varunsood...@gmail.com> wrote: > > Hi > > We were wondering if we should move away from Active MQ and adopt Kafka but > then I learnt that Kafka is not JMS and it does not support Multi-Protocols. > > Is that true? > > And if above is true, how such use cases (JMS and Multiprotocol) are > handled in Kafka? > > Also, people who moved away from Active MQ to kafka, what has been your > experience? > > Thank You!
