...
Starting with the 0.8 release we are maintaining all but the jvm client external to the main code base. The reason for this is that it allows a small group of implementers who know that language to quickly iterate on that client. Having these maintained centrally was becoming a bottleneck as the main committers can't hope to know every programming language that has a client. This lead to a scenario where the committers were attempting to review and test code they didn't understand. We are instead moving to the redis/memcached model which seems to work better at supporting a rich ecosystem of high quality clients.
If you are aware of other clients not listed here (or are the author of such a client), please add it here. Please also feel free to help fill out information on the features the client supports, level of activity of the project, level of documentation, etc.
For 0.8.x
0.8 changes the protocol fairly substantially. This version hasn't been released yet. The new protocol is documented here. A number of clients are in progress, and we will update when they are complete.
...
https://github.com/quipo/kafka-cpp
Erlang
erlkafka is a kafka client written in erlang
https://github.com/milindparikh/erlkafka.git
Maintainer: Milind Parikh *License: BSD, LGPL
Also:
https://github.com/wooga/kafka-erlang
PHP
PHP library with Consumer (simple and Zookeeper-based), Producer and compression support (release notes).
...
Also:
https://github.com/dannycoates/franz-kafka
Erlang
erlkafka is a kafka client written in erlang
https://github.com/milindparikh/erlkafka.git
Maintainer: Milind Parikh
*License: BSD, LGPL
Also:
https://github.com/wooga/kafka-erlang
Client Libraries Previously Supported
...