Moving topic from old guide per CDK-753

The first relevant point is that Kite's API is a layer above the file format. It isn't enough to have a good file format, users need a reliable and standard file layout as well to take advantage of Hadoop.

The second relevant point is that we are choosing a Avro for our object representation. That's simply because Avro did a great job and has a good for a variety of uses (generic, specific, reflect).

Another thing that is relevant is that there are protobuf and thrift libraries that work with Avro and we want to eventually support them.