27.

Why to use Thrift Less time wasted by individual developers No duplicated ne tworking and protocol code less time dealing with boilerplate stuff Write your c lient and server in about 5 minutes Less maintenance One networking code base th at needs maintenance Fix bugs once, rather than repeatedly in every server Divis ion of labour Work on high-performance servers separate from applications Common toolkit Code reuse and shared tools 28. Why to use Thrift Cross-language serialization with lower overhead than alte rnatives such as SOAP due to use of binary format A lean and clean library. No f ramework to code to. No XML configuration files. The language bindings feel natu ral. For example Java uses ArrayList<String>. C++ uses std::vector<std::string>. The application-level wire format and the serialization-level wire format are c leanly separated. They can be modified independently. 29. Why to use Thrift The predefined serialization styles include: binary, HTTPfriendly and compact binary. Soft versioning of the protocol. No build dependenc ies or non-standard software. No mix of incompatible software licenses. 30. Limitations / Non-Features Is struct inheritance/polymorphism supported? No, it isn t Can I overload service methods? Nope. Method names must be unique. Heter ogeneous containers Not supported Is there any enough documentation on Thrift de velopment? I think this is one weak area.