We’ve (meaning @bgmarx) explored this option for our internal service communication. There are a few use cases where it would be really beneficial but we also had several payloads that were faster to encode in JSON and resulted in smaller payloads. These requests are outside the norm so it shouldn’t be taken as a indictment of ETF. Just a reminder that its always important to measure your specific use case. Because of those payloads and because it would require a large change throughout our stack we decided not to pursue it further for the time being.
