This is not really true. Yes, you do have to translate your data structures to Thrift structures, but legacy systems generally require quite a bit of shimming to get them to be accessible anyway. One of the big benefits that Thrift offers you is cross language access.
If you are totally hung up on using your current data structures, take a look at Avro. It is able to use reflection to figure out how to serialize existing java objects. On Sat, Mar 6, 2010 at 2:04 AM, Jeff Zhang <[email protected]> wrote: > So it is better to adopt Thrift at the beginning of project. Thrift can not > be used for legacy system, except you change the API. >
