You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by GitBox <gi...@apache.org> on 2020/05/15 11:56:42 UTC

[GitHub] [trafficserver] brbzull0 commented on issue #6633: Use JSON-RPC based interface for administrative API.

brbzull0 commented on issue #6633:
URL: https://github.com/apache/trafficserver/issues/6633#issuecomment-629193865


   > What are the trade-offs between JSON-RPC and straight GRPC? My perspective would be that GRPC dominates the RPC space and has by far better tooling, libraries and access than anything else.
   
   imo, to compare both solutions we should first put a scope on grpc, do we want to use the encoding they recommend by default which is proto buff? or just JSON as encoder?
   Transport, grpc uses h2, is this something we want? jsonrpc is transport agnostic so we can pick what we think is better.
   Performance, grpc seems super on this, will we be taking advantage of this? 
   
   Anyway, the plan is to have a 'lighting talk' during the Summit so we can keep talking about this.
   
   I wasn't part of the first discussion on this topic, but I found [this](https://www.mail-archive.com/dev@trafficserver.apache.org/msg14119.html) from 2018.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org