Hi Dave, this is really helpful, useful, informative and cool.

One thing I wanted to float is "client" vs "client" meaning a new (or
existing) language implementing a new API vs wrapping an existing API and
confusion between the two.

I think your post is geared towards the former which is really awesome
because it helps devs jump into Kafka (I found it really helpful myself
learned some things strait up, always good).

I was toying this weekend about adding
https://github.com/andrix/python-snappy to the python client and building a
python example for that client.... I am in progress building a producer to
stream our data but not sure yet if python might make more sense for me
than scala but I have to go through it all some more (nothing Kafka
specific just in my implementation needs and if I do it in scala will do
the example in scala).

Either way I want to contribute it back into the codebase however the
examples directory seems to only be for Java (doh), I was not sure how we
could deal with this so we could add examples for scala, python, ruby, cpp,
pyp, go, c#, etc (javascript? node.js? =8^) )  I bring this up because I
think it is an important part of adoption and have found while moving Kafka
into my own development cycles these examples/samples (maybe create a new
samples directory, dunno) would have been REALLY helpful.  Documentation is
great, code is just as good if not better to look at it IMHO

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/

On Wed, Nov 23, 2011 at 6:32 PM, David Ormsbee <d...@datadoghq.com> wrote:

> Hi folks,
>
> Inspired by the Wire Format wiki entry, I recently created a draft of
> "Writing a Client for Kafka":
>
>  http://readthedocs.org/docs/brod/en/latest/spec.html
>
> I tried to make it the document that I wish we had at Datadog when we
> were total Kafka newbies writing client code. It's still very rough
> and littered with "FIXME" notes where I've written things from my
> understanding without verifying them with tests. I should be filling
> all these gaps in soon, as we're planning to add a lot of
> functionality to our Python client in the coming weeks.
>
> Comments and corrections would be greatly appreciated. :-)
>
> Thank you very much to the Kafka devs. We've been using Kafka a great
> deal at Datadog, we're extremely happy with it, and we're looking
> forward to contributing in our own way. We'll make an announcement as
> soon as we feel our Python client is ready for community use.
>
> Take care.
>
> Dave
>

Reply via email to