The power of the consumption APIs and the general performance offered by
Kafka is only useful if you can send the data to Kafka and use the consumer
APIs. Apache Storm will not solve the problem if you are trying to avoid
using the Kafka consumer APIs. I would rethink the architecture you
currently have and see if the JMS queues can be replaced by Kafka
consumers. This would require a plugin that could pull data out of the
source JMS queue, if there isn't a way to replace that as well.
On Wed, Aug 13, 2014 at 6:06 AM, Andrew Longwill <
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB