gRPC vs JSON-RPC: What are the differences?
Developers describe gRPC as "A high performance, open-source universal RPC framework". gRPC is a modern open source high performance RPC framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking... On the other hand, JSON-RPC is detailed as "A remote procedure call protocol encoded in JSON". It is a very simple protocol, defining only a few data types and commands. It allows for notifications (data sent to the server that does not require a response) and for multiple calls to be sent to the server which may be answered out of order.
gRPC and JSON-RPC belong to "Remote Procedure Call (RPC)" category of the tech stack.
gRPC is an open source tool with 22.4K GitHub stars and 5.24K GitHub forks. Here's a link to gRPC's open source repository on GitHub.
Slack, 9GAG, and Policygenius are some of the popular companies that use gRPC, whereas JSON-RPC is used by Qurami, eleme, and TelebidPro. gRPC has a broader approval, being mentioned in 79 company stacks & 114 developers stacks; compared to JSON-RPC, which is listed in 7 company stacks and 3 developer stacks.
Sign up to add or upvote prosMake informed product decisions
What is gRPC?
What is JSON-RPC?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions