I am unsure whether to specify a new service in terms of Thrift or JSON/HTTP.
I have read an elaboration by an original Thrift author, Mark Slee, of relevant decision points on this matter,* including expected gain from the advantages of strong typing, performance, serialization efficiency. versioning support and server implementation, but I do not know how assess those relative benefits for my new service, now. Allowing an even chance that the benefits of a Thrift service implementation would later be judged superior to JSON/HTTP, is it still preferable to specify the service (test specs) in terms of JSON/HTTP and migrate later? Or, alternatively, might it be better to specify Thrift services and 'layer on’ a JSON/HTTP interface? * http://www.quora.com/What-are-the-use-cases-for-Thrift-i-e-what-reasons-are-there-to-consider-using-Thrift-when-one-could-rely-on-JSON-and-standard-HTTP-requests <http://www.quora.com/What-are-the-use-cases-for-Thrift-i-e-what-reasons-are-there-to-consider-using-Thrift-when-one-could-rely-on-JSON-and-standard-HTTP-requests>
