One big benefit of JSON-RPC is batch requests (https://www.jsonrpc.org/specification#batch). I'm not sure REST could match the efficiency of JSON-RPC in that respect. For example, with JSON-RPC you can query 100 requests in a single connection, while you'd need 100 http(s) connections to get the same results with REST.
You are viewing a single comment's thread from:
Its not a benefit for public nodes, its a huge detriment. Its not possible to cache the large request, it must be parsed and unpacked. REST absolutely can match the "efficiency" by utilizing https/2 and async & parallel programming on the client side.
The result is cache friendly server behaviour and excellent client performance.
Further, rate limiting is much harder when someone tries to batch 100 fat account history requests. Its much easier to do this with parallel requests.