BTW, Wikimedia uses varnishkafka to produce http requests to Kafka, and we are
pretty happy with it.
https://github.com/wikimedia/varnishkafka
On Mar 5, 2015, at 13:09, Ewen Cheslack-Postava e...@confluent.io wrote:
Yes, Confluent built a REST proxy that gives access to cluster metadata
I read the description of the new Confluent Platform and it briefly
describes some REST access to a producer and a consumer.
Does this mean there is a new process(es) running (Jetty based)?
This process integrates both the consumer and producer libraries?
Thanks
Julio Castillo
NOTICE: This
Yes, Confluent built a REST proxy that gives access to cluster metadata
(e.g. list topics, leaders for partitions, etc), producer (send binary or
Avro messages to any topic), and consumer (run a consumer instance and
consume messages from a topic). And you are correct, internally it uses
Jetty and
