4 ms·
The author's main beef in this article are the more exotic HTTP verbs. I don't think that gets at the crux of why REST sucks for Web Services/APIs. The core p
by restdoesnotsuck 8y ago
The author's main beef in this article are the more exotic HTTP verbs. I don't think that gets at the crux of why REST sucks for Web Services/APIs.
The core problem is that REST (which, recall is a description of the web architecture) requires HATEOAS. JSON doesn't naturally implement a hypertext in the way that HTML does and, further, the other end of a JSON call is almost certainly code, rather than a human, and thus isn't able to take advantage of this feature anyway.
Here are a few articles on this general idea:
http://intercoolerjs.org/2016/01/18/rescuing-rest.html http://intercoolerjs.org/2016/01/18/rescuing-rest.html
http://intercoolerjs.org/2016/05/08/hatoeas-is-for-humans.html http://intercoolerjs.org/2016/05/08/hatoeas-is-for-humans.ht...
- droussel 8y agoI've designed and implemented a few REST api over the years that both made use of json for resource representations and also used hyperlinks. You do need to create your own media types and document them properly though, but media types and relations are at the core of any good REST APIs.