grpc vs json-rpc #12641
Replies: 2 comments 3 replies
-
Each node exposes a Tendermint endpoint which talks JSON-RPC: https://docs.cosmos.network/main/core/grpc_rest.html#tendermint-rpc. So it's not "instead", but both can run together, or you can configure your node to run only one. 2 advantages that gRPC has in my opinion:
|
Beta Was this translation helpful? Give feedback.
-
I think most of the points you listed apply equal well to the way we use gRPC if not better. Also, we have types so client code can be generated. We're using protobuf for storage so gRPC is an obvious choice and is more performant. I'm also not sure all the points you made even apply to json-rpc (unless things have changed significantly recently), sounds more like REST/OpenAPI which we support via grpc-gateway. |
Beta Was this translation helpful? Give feedback.
-
Hey guys,
Wondering what's the value running grpc instead of json rpc?
Afaik json-rpc is:
It seems to me like using grpc (not even going to talk about amino hrmm) makes the learning curve steeper for new devs to join in. The depreciation of native standardised restful and rpc APIs seems like a disaster for the ecosystem approachability. Would be interested to hear the arguments in favor
Beta Was this translation helpful? Give feedback.
All reactions