Monday, January 15, 2024

web: should REST APIs be "hypermedia"

interesting podcast episode

HATEOAS corpus (Changelog & Friends #24) |> Changelog

Roy Fielding - Wikipedia, a co-author of HTTP spec,
and person who defined "REST" style of interface
did intend to provide much more "context" information to API call responses, "hypermedia"

Most of REST API's don't have any, just plain JSON data.

Neither human readable, nor efficient, not extensible, not representing any "state".

It is "popular" because it is popular, like some media personalities.
Maybe "too simple?"

HATEOAS - Wikipedia

Hypermedia as the engine of application state (HATEOAS) is a constraint of the REST application architecture that distinguishes it from other network application architectures.

REST (Representational state transfer) is a software architectural style that was created to guide the design and development of the architecture for the World Wide Web. REST defines a set of constraints for how the architecture of a distributed, Internet-scale hypermedia system, such as the Web, should behave. The REST architectural style emphasises uniform interfaces, independent deployment of components, the scalability of interactions between them, and creating a layered architecture to promote caching to reduce user-perceived latency, enforce security, and encapsulate legacy systems

links from podcast