JSON-RPC is widely used for access to the application with the remote procedure call (RPC) and using JSON to define the parameters you want to get. It’s widely used because of its benefits compared to REST and other standards: platform-agnostic type, quick development and simple handling, explainable results, and straightforward data transfer. Here you can find the typical JSON-RPC example.
Yes, it’s still quite popular among developers. It’s widely used in blockchain and microservices, where quick communication between applications and other structural blocks of infrastructure is essential. The variety of JSON-RPC methods can be attributed to one of the JSON-RPC 1.0 or 2.0 versions.
When the call is initiated, the server has to send a Response, except for Notifications. The typical JSON-RPC response is a JSON Object that has a few members: an ID (that’s the same as in Request Object), jsonrpc specifying “2.0” version, error and result, which are mutually exclusive.
No, you can’t consider JSON-RPC protocol an API. But it can be incorporated into an API as a part responsible for the connection. Our JSON RPC Caching Proxy is an excellent example of this implementation.
The simplest JSON-RPC example from real life is a kind of information kiosk at the train station that can print tickets, too. Passengers must contact the information kiosk first, and only then they will be distributed for their nodes-as-platforms to work with the infrastructure further. The JSON-RPC protocol works fast and well with all requests to nodes, not delaying any of them.