Representational State Transfer – better known as REST – is one of the most important programming paradigms of modern web development. The architectural style that Roy Fielding invented in his 2000 dissertation, serves the primary purpose of adapting web applications as optimally as possible to the requirements of the modern web. Because REST has gained noticeable popularity and importance in the recent past, many web project operators have been increasingly attempting to implement the concept to the best of their ability. However, the results of these efforts are not often 'RESTful' or 'REST-compliant' since certain principles and properties (such as HATEOAS) have not been implemented adequately.
HATEOAS is an acronym that stands for 'Hypermedia as the Engine of Application State'. This term, introduced by Fielding as part of his REST definition, describes one of the key REST properties: since the architecture style is supposed to provide a universal interface, HATEOAS requires the REST client to only move through the web application by following URIs (Uniform Resource Identifiers) in hypermedia format. If this principle is implemented, the client does not require any further information apart from a basic understanding of hypermedia in order to be able to interact with the application or the server.
The individual URIs are provided…
By implementing the HATEOAS principle, the interface of a REST service can be adapted at any time. This is an important advantage of this architecture compared with other application structures, for example, those based on SOAP (Simple Object Access Protocol).
In order to classify HATEOAS and its significance for REST applications, you have to take a look at the overall construction. In his concept, Fielding describes a total of five basic principles that must be fulfilled in order to make a service REST-compliant.
In order to protect your privacy, the video will not load until you click on it.
In any case, there must be a client-server structure that also enables stateless communication between the server and clients (i.e. requests are handled without referring to previous queries). In addition, the service should have a multi-layered structure and take advantage of HTTP caching to make it as easy as possible for the accessing client to use the service. Finally, implementing a uniform interface to compulsory tasks, which has already been mentioned, is also part of the package.
Fielding specifies four properties for the connection between server and client:
HATEOAS is, therefore, one of the elementary features of REST APIs and is indispensable for any REST service.
For more information on REST, see our basic article on the topic.
In order to make the HATEOAS concept a little more tangible, the concept’s implementation will be illustrated in the following section using a web store as an example. As is typical for web applications, HATEOAS is implemented by placing hyperlinks. These cross-references between two documents or cross-references to another position in the same document are marked in the HTML code like this:
<a href="URI">Link-Text</a>Linked media, such as text, graphics, audio, and video, are referred to as hypermedia. Web applications are mainly simple text documents in HTML format that can also be regarded as states of these applications. Within the framework of the REST philosophy, the individual documents can always be addressed with a unique URL. If you transfer the concept to an ordinary online store, the following will result:
The document describing the state 'shopping cart' has a permanently assigned URI, for example: 'https://example.org/shoppingcart'. In the same style, there are also URIs for individual items that can be placed in the shopping cart – such as 'https://example.org/item/1', 'https://example.org/item/2', etc. Another possible state is the customer account, which can be accessed directly from the shopping cart and could have the following URI: 'https://example.org/customer/1'. Each individual document also contains links or hyperlinks to actions that the user could perform next.
In order to keep with the present scenario, this means that the shopping cart document also contains cross-references to the article and customer URIs. These could, in turn, contain further links to manufacturers or contractual documents. By means of a GET request, the client then moves through the store, or in this case, through the shopping cart thanks to the various hyperlinks, as the following simplified image illustrates:
In the case of a REST service, in which the HATEOAS principle was followed as required by Fielding, the user only needs to know the start URI in order to be able to take advantage of the offer as planned by the developer.
On the basis of the above-mentioned web store structure, the possible communication between client and server can also be explained. The client application makes the following request in order to obtain an XML representation of the shopping cart state:
GET 'https://example.org/shoppingcart' HTTP/1.1
Host: 'https://example.org'
Accept: application/xmlThe server’s response could then look like this:
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 256
<?xml version="1.0"?>
<shoppingcart>
<shoppingcart_number>1</shoppingcart_number>
<link rel="account" href="https://example.org/customer/1" />
<link rel="item1" href="https://example.org/item/1" />
<link rel="item2" href="https://example.org/item/2" />
</shoppingcart>
Combining different application systems has become increasingly important over the past few years. This trend is especially due to the increasing number of web applications being developed. In order to react to this trend, many different web services were developed that make data transfer across multiple systems possible. The Representational State Transfer (REST) is an architectural style that...
NoSQL databases have long since been serious competitors to classic relational database systems, like MySQL. They replace the strictly-defined storage structures of traditional models through flexible saving procedures. This allows data pools to be easily distributed onto multiple servers in order to guarantee high availability of web applications. But are these new systems really all that they’re...
Microservice architecture has established a relatively new way of structuring complex applications. Instead of dealing with huge source code, you build a program made of many self-contained services. This also leads to a restructuring of workflow in terms of agile project management. What are the pros of this method? This article will explore how microservices are designed, what advantages they...
Applications on the web need interfaces in order to exchange data. If you run a web project yourself and want to grant other programs access to certain data sets, an API (application programming interface) like this is essential. Established concepts such as REST or SOAP are often used in development – but there are alternatives, as GraphQL proves.
With continuous delivery, software developers automate the process of development, quality assurance, testing, production, and delivery. This gives them the opportunity to deliver software to the customer at a much earlier stage of development while the program continues to be developed. The continuous delivery pipeline required for this is divided into different test phases. What are these, what...
Provide powerful and reliable service to your clients with a web hosting package from IONOS.
View packages