-1 Kafka's development model is a good fit for critical path and well-established APIs. It doesn't work as well for add-ons that need to rapidly evolve. Merging communities with different development pace and models rarely ends well - I think the REST Proxy will benefit from being a separate project.
On Tue, Oct 25, 2016 at 11:16 PM, Harsha Chintalapani <ka...@harsha.io> wrote: > Hi All, > We are proposing to have a REST Server as part of Apache Kafka > to provide producer/consumer/admin APIs. We Strongly believe having > REST server functionality with Apache Kafka will help a lot of users. > Here is the KIP that Mani Kumar wrote > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 80:+Kafka+Rest+Server. > There is a discussion thread in dev list that had differing opinions on > whether to include REST server in Apache Kafka or not. You can read more > about that in this thread > http://mail-archives.apache.org/mod_mbox/kafka-dev/201610.mbox/%3CCAMVt_ > aymqeudm39znsxgktpdde46sowmqhsxop-+jmbcuv7...@mail.gmail.com%3E > > This is a VOTE thread to check interest in the community for > adding REST Server implementation in Apache Kafka. > > Thanks, > Harsha > -- *Gwen Shapira* Product Manager | Confluent 650.450.2760 | @gwenshap Follow us: Twitter <https://twitter.com/ConfluentInc> | blog <http://www.confluent.io/blog>
