REST HATEOAS Debate
Comments debate the true meaning of REST APIs, criticizing the common 'HTTP + JSON' interpretation and emphasizing hypermedia, HATEOAS, and Roy Fielding's original constraints from his dissertation.
Activity Over Time
Top Contributors
Keywords
Sample Comments
REST is missing. Should be about hypermedia. Now means JSON API.See: https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypert...
How does he talk about REST and totally forget about HATEOAS...
"REST = HTTP + JSON" is absolute nonsense!
I think true REST APIs should be called a HATEOS APIs these days to disambiguate. REST just means GET/POST json at this point.
This answer is correct, but lacks context. REST wasn't conceived with APIs in mind. In fact, it's an awful fit for APIs, as many of the other comments point out. Rather, REST today is a buzzword that took on a life of its own, bearing only superficial resemblance to the original ideas.HATEOAS is a generalization of how something like a website would let a client navigate resources (through hyperlinks). It requires an intelligent agent (the user) to make sense. Without HATEOAS
I must disagree. REST is defined by four interface constraints: http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch... and identification of resources is the first principle. This functionality is implemented by URLs in HTTP and is therefore critical. HATEOAS (the 4th principle) also seems to be gravely misunderstood. It only means that the API shou
Are we talking about REST with HATEOAS? If we are, it’s apples to oranges.
this guy agrees with you https://www.tbray.org/ongoing/When/201x/2018/11/18/Post-REST
This is an HTTP API, not a REST API.http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...
It's not really REST if there's no link in sight. Why not just call it a HTTP API or a Webservice?