I haven’t done benchmarks here, but I actually run both HTTP/JSON and a TCP/Binary on the same server. They both get the same instance of the service implementation.
There are some good benchmarks here though. https://github.com/m1ch1/mapkeeper/wiki/Thrift-Java-Servers-Compared -Matt > On Jun 3, 2016, at 12:52 AM, Gajanan H <[email protected]> wrote: > > Hi guys, > > I have been using Thrift for some time now. It works great! All my services > till date are running with TSocket transport and TBinaryProtocol. > > Now I am having to move to HTTP transport and JSON protocol. So I have the > following questions. It would be great if someone could provide answers, or > point me to resources where these questions are answered. > > 1. What kind of performance hits will I be taking when I move to > HTTP/JSON from TCP/Binary ? > 2. Are there any other disadvantages of using HTTP/JSON? Eg: Not being > able to use Nonblocking server. > 3. Have there been any studies on the performance comparisons of > HTTP/JSON vs TCP/Binary? > > Greatly appreciate your help. > > Regards, > Gajanan
