[KAFKA-1995] JMS to Kafka: Inbuilt JMSAdaptor/JMSProxy/JMSBridge (Client can speak JMS but hit Kafka)

• Type: Wish
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.9.0.0
• Component/s: core
• Assignee: Unassigned
• Reporter: Rekha Joshi
• Created: 02/Mar/15 05:56
• Updated: 17/May/17 12:59

Description

Kafka is a great alternative to JMS, providing high performance, throughput as scalable, distributed pub sub/commit log service.
However there always exist traditional systems running on JMS.
Rather than rewriting, it would be great if we just had an inbuilt JMSAdaptor/JMSProxy/JMSBridge by which client can speak JMS but hit Kafka behind-the-scene.
Something like Chukwa's o.a.h.chukwa.datacollection.adaptor.jms.JMSAdaptor, which receives msg off JMS queue and transforms to a Chukwa chunk?

I have come across folks talking of this need in past as well.Is it considered and/or part of the roadmap?
http://grokbase.com/t/kafka/users/131cst8xpv/stomp-binding-for-kafka
http://grokbase.com/t/kafka/users/148dm4247q/consuming-messages-from-kafka-and-pushing-on-to-a-jms-queue
http://grokbase.com/t/kafka/users/143hjepbn2/request-kafka-zookeeper-jms-details

Looking for inputs on correct way to approach this so to retain all good features of Kafka while still not rewriting entire application.Possible?