A json payload can be seen from several perspectives:

- as some kind of object (e.g. jackson  JSonNode)
- as a string
- a byte array

Imho all depends on what "perspective" you are using.

Assuming that you are not working directly with byte arrays (in this case
you could write a simple Byte array encoder / decoder) you can create

- a String encoder / decoder (I don't remember if kafka dist already has
- a little bit more complex Json encoder / decoder that handles the
serialization (byte array to object and viceversa) behind the scenes.

On 23 Jun 2013 13:08, "Oleg Ruchovets" <[EMAIL PROTECTED]> wrote:
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