JSON-RPC vs JSON

Question

I am familiar with Restful services created using json as the medium. But today I heard a new term "JSON-RPC" which I am unfamiliar with.

On doing some research it looks as if JSON-RPC is similar to SOAP web services where you have a defined contract between the requestor and the responder and the requestor has to have a client in the form of a jar like I remember I used to have to do when I used Apache Axis SOAP web services (even though there would not be a wsdl).

So whilst it can be good if you want to enforce a really strong contract between two parties it can be cumbersome to change because you have to regenerate stubs and distribute stubs to any potential new requestors?

Have I summed it up correctly?

thanks

just to add more [info](http://stackoverflow.com/questions/15056878/rest-vs-json-rpc) — Ankur Singhal, Sep 10 '14 at 03:40
So i was correct when I said that you need a client jar file to call a JSON-RPC restful web service? — Richie, Sep 10 '14 at 03:43

score 0 · Answer 1 · answered Jun 14 '16 at 21:51

JSON-RPC is indeed similar to SOAP. It is just that normally you have no explicit contract and no service description file and the protocol is as simple as it gets.

This is what a JSON-RPC 1.0 request looks like: {"method": "echo", "params": ["Hello JSON-RPC"], "id": 1}

JSON-RPC vs JSON

1 Answers1