REST vs JSON-RPC? [closed]

by

The fundamental problem with RPC is coupling. RPC clients become tightly coupled to service implementation in several ways and it becomes very hard to change service implementation without breaking clients:

  • Clients are required to know procedure names;
  • Procedure parameters order, types and count matters. It’s not that easy to change procedure signatures(number of arguments, order of arguments, argument types etc…) on server side without breaking client implementations;
  • RPC style doesn’t expose anything but procedure endpoints + procedure arguments. It’s impossible for client to determine what can be done next.

On the other hand in REST style it’s very easy to guide clients by including control information in representations(HTTP headers + representation). For example:

  • It’s possible (and actually mandatory) to embed links annotated with link relation types which convey meanings of these URIs;
  • Client implementations do not need to depend on particular procedure names and arguments. Instead, clients depend on message formats. This creates possibility to use already implemented libraries for particular media formats (e.g. Atom, HTML, Collection+JSON, HAL etc…)
  • It’s possible to easily change URIs without breaking clients as far as they only depend on registered (or domain specific) link relations;
  • It’s possible to embed form-like structures in representations, giving clients the possibility to expose these descriptions as UI capabilities if the end user is human;
  • Support for caching is additional advantage;
  • Standardised status codes;

There are many more differences and advantages on the REST side.

More Related Contents:

  1. What exactly is RESTful programming?
  2. Best practices for API versioning? [closed]
  3. If REST applications are supposed to be stateless, how do you manage sessions?
  4. RESTful URL design for search
  5. Free Rest API to retrieve current datetime as string (timezone irrelevant) [closed]
  6. Design RESTful query API with a long list of query parameters [closed]
  7. Transactions in REST?
  8. How to QUEUE a new build using VSTS REST API
  9. What is RESTful programming?
  10. How to understand “RESTful API is stateless”?
  11. Groovy built-in REST/HTTP client?
  12. RESTful way to create multiple items in one request
  13. How to construct a REST API that takes an array of id’s for the resources
  14. Why the slow WADL uptake? [closed]
  15. Azure Websites Kudu REST API – Authentication
  16. How to format Swagger 2.0 text descriptions?
  17. Update an entire resource collection in a REST way
  18. What are the best/common RESTful url verbs and actions?
  19. How should the header X-DocuSign-Authentication be used for REST and SOAP?
  20. Restful way for deleting a bunch of items
  21. When is it appropriate to respond with a HTTP 412 error?
  22. Swagger documentation with JAX-RS Jersey 2 and Grizzly
  23. How one could use server side sorting and paging with Azure Mobile Services
  24. Can I change the headers of the HTTP request sent by the browser?
  25. When in my REST API should I use an envelope? If I use it in one place, should I always use it?
  26. Swagger UI passing authentication token to API call in header
  27. The MAC signature found in the HTTP request ‘…’ is not the same as any computed signature
  28. Response status code for searches in REST APIs
  29. Hyphen, underscore, or camelCase as word delimiter in URIs?
  30. REST API DESIGN – Getting a resource through REST with different parameters but same url pattern

Leave a Comment