3 ms·
Lots of developers in general doesn't seem to understand the concept of a REST API. What are the benefits? Why are we doing this at all? How to do it properly?
by kissgyorgy 6y ago
Lots of developers in general doesn't seem to understand the concept of a REST API. What are the benefits? Why are we doing this at all? How to do it properly?
Most APIs are not REST, just some RPC-like APIs over HTTP.
When you have a tool like this, it's just easier to use it and call it a day - without thinking too much or learning the concepts properly.
- deleted 6y ago[deleted]
- avinassh 6y ago> Most APIs are not REST, just some RPC-like APIs over HTTP. Can you elaborate this part? Does PostgREST does that? If not, any example of it
- corytheboyd 6y agoI think the point is that many people in the wild conflate the term “REST API” with “arbitrary interaction over HTTP”. We’ve all seen examples, the one-off endpoint to fetch that little tertiary bit of data, that one-off POST to invalidate a cache. None of that is REST
- abraae 6y agoTo REST purists, APIs must use HATEOAS to be considered REST.
- masklinn 6y ago"HATEOAS" is pretty much the only thing REST contains. "REST API" without HATEOAS has no meaning, it's just a stand-in for "good HTTP citizen" (if even that).
- philwelch 6y agoREST isn’t an architecture for designing HTTP API’s; it’s an architecture for designing HTTP itself. https://twobithistory.org/2020/06/28/rest.html https://twobithistory.org/2020/06/28/rest.html