I am very cautious of Thrift's custom network stack. We have a java backend service that gets thousands of requests per second per node and where latency is of

I am very cautious of Thrift's custom network stack. We have a java backend service that gets thousands of requests per second per node and where latency is of upmost importance. We tested thrift for communication between the backend service and the front end web code, however we saw an increase in failed requests and latency compared to a server written using netty. For us, using netty and Protocol Buffers works much better, but maybe we were using Thrift wrongly.