Uniform Interface ensures that the data is transferred in a standardized form.This is useful for scalability as well as security. The API design should ensure that the client and server don't know whether or not they are communicating directly with each other, or there are other layers of intermediaries between them. This improves the performance and scalability of the system as the request overhead is reduced. This states that responses clearly state whether or not they are cacheable to prevent future irrelevant requests to the server as the data is already cached on the client-side. This greatly improves the system's scalability. This means that the client and server should be two separate and independent entities. This implies that a request to a server needs to have all the necessary information to process it as servers do not store client request data. REST APIs abide by the following design constraints: Each resource usually has two URLs, one for a single resource entity or instance and one for a collection of resources. The name of the resources should be nouns such as api/products and not verbs such as api/getProducts.

The endpoints include the name of the resource being requested. Roy Thomas Fielding.Ī REST API focuses on providing clients with resources from the server. The Representational State Transfer (REST) style is an abstraction of the architectural elements within a distributed hypermedia system. However, the most common type of API is the HTTP API that uses HTTP(Hypertext Transfer Protocol) as the transport protocol between the client and server. There are different types of APIs depending on the transport protocol used. The client sends a request to the server that sends back a response with data in JSON or XML format. It is a set of protocols that allows two systems to communicate to share resources and services. An API is an acronym for Application Programming Interface. The two design architectures are widely used in Web services to build APIs. In contrast, REST allows the client to specify Content-types or accept headers. RPC implementations require payloads of certain data types such as XML for XML-RPC. REST supports hypermedia which are hyperlinks included in the response to provide the client with links to other related resources whereas RPC does not. However, RPC only supports GET and POST requests.

REST utilizes HTTP methods GET, POST, PUT, PATCH, and DELETE to perform CRUD operations.

REST stands for Representational State Transfer and RPC stands for Remote Procedural Call. In this article, we have covered the differences between REST and RPC.

Slack client response in xml format