HATEOAS

HATEOAS

HATEOAS stands for Hypermedia as the Engine of Application State. It is a constraint that explains the interaction between a user agent and an origin server. It allows a resource to be related to none or more resources, and relations are specified as hypermedia links. HATEOAS enables autonomous handling of arbitrary service interfaces, methods, and data types to be consumed using approaches like WADL or HATEOAS.From: Design and Construction of an RFID-enabled Infrastructure [2019], RESTsec: a low-code platform for generating secure by design enterprise services [2018], IoT Automation [2019]

Cyber physical systems implementation for asset management improvement: A framework for the transition

View Chapter

Purchase Book

Published in Stein Haugen, Anne Barros, Coen van Gulijk, Trond Kongsvik, Jan Erik Vinnem, Safety and Reliability – Safe Societies in a Changing World, 2018

L. Villar-Fidalgo, A. Crespo Márquez, V. González Prida, A. De la Fuente, P. Martínez-Galán, A. Guillén

In the software level, the continuous evolution of information technologies is a risk factor and the use of open and standard methodologies for communications, like REST APIs with HATEOAS to exchange data, based on JSON or XML should be a priority. A wrong step in this direction could endanger the rest of the project by making CPS unable to communicate among them.

Flexible simulation of traffic with microservices, agents & REST

View Article

Journal Information

Published in International Journal of Parallel, Emergent and Distributed Systems, 2023

Martynas Jagutis, Seán Russell, Rem Collier

The issue of constructing URLs is not new. In fact, it is one of a number of issues raised by Fielding [19] when describing REST. In particular, he describes best practice for the implementation of REST based applications through the concept of Hypermedia As The Application Of Engine State (HATEOAS). Fielding argues that the construction of URLs should be the responsibility by the microservice (he used the word server here) that the URLs refer to and should be provided by that service as part of the resource representation.

Explore chapters and articles related to this topic

Cyber physical systems implementation for asset management improvement: A framework for the transition

Flexible simulation of traffic with microservices, agents & REST