What if the web were not RESTful?

Abstract

So-called RESTful services are in widespread use both on the Web, and increasingly, in large enterprises. We say "so-called" because in reality, most of these services are not very RESTful. Those active in the REST community know well where these interfaces fail to meet REST principles, however, true understanding remains only in this relatively small community. Unfortunately, the result is a set of interfaces that are ultimately limited in their use, and the deficiencies are not usually recognized until it is too late to make the necessary changes. Our experience has shown that individuals are not being deliberately neglectful, rather, they simply do not know what they do not know. Everyone thinks they "get REST", after all, using HTTP to move XML or JSON payloads over the network is very simple. We have found that most individuals begin to understand the nuances of REST when they are explained and they almost always ask for resources that further explain these concepts. Certainly, materials are available, however the best ones are rather substantial in size lessening the chance that many people will read them.In this paper we take a fresh approach to explaining the core principles of REST, by describing a World Wide Web that fails to meet these tenets. We look at each key element, resource orientation, the uniform interface, media types and hyperlinking, and imagine the consequences of not abiding by the REST architectural style on the end user or tools developer of the Web. We then do a similar analysis in the context of Web services and programmatic consumers, reexamining each REST characteristic, describing common mistakes and suggesting improvements. We have found that in discussions, the analogy of the World Wide Web has been very effective at explaining REST.

Redefining Data Provider: The REST approach To solve Indonesia Lecturer administrative problems

“…Representational State Transfer (REST), is bubbling protocol to serve an information with lightweight bandwidth consumption and rock solid protocol to support the use of web as distributed systems [2,3]. The importance of REST paradigm, made REST the best approach for distributed systems.…”

A reliability-aware framework for service-based software development

“…This design is seen as highly successful and important as most of the current world wide web runs using REST. From this dissertation, most literature has agreed that the following four architectural principals summarize REST [18]:…”

“…With this addressing scheme, an interface is now required to allow for external users to accesses and manipulate the resources. In REST, this is done through a standard uniform interface [18]. The standard uniformity of this interface is important as it allows for a consistent interoperability among different providers.…”

The fallacy of the multi-API culture

“…Furthermore, the specification describes whether or not these methods have qualities such as safeness and idempotence that need to be Note: Representations can include (links to) other resources, as is the case here with the HTML representation. Note how the target of the link is the resource (which is stable) and not any particular representation (which can be different) respected (Davis, 2012). This limited set of methods makes it easy for any party to understand a message by itself, in contrast to programming languages where custom method names can be associated with specific semantics (Van Roy and Haridi, 2004).…”

“…To contribute to self-descriptiveness, HTTP only defines a limited number of methods that may be used in messages, such as GET (retrieving a representation of a resource), POST (creating or annotating a resource), PUT (storing a resource), and DELETE (removing a resource). Furthermore, the specification describes whether or not these methods have qualities such as safeness and idempotence that need to be (Davis, 2012). This limited set of methods makes it easy for any party to understand a message by itself, in contrast to programming languages where custom method names can be associated with specific semantics (Van Roy and Haridi, 2004).…”