PostgREST: REST API for any Postgres database

Re:PostgREST: REST API for any Postgres database by kissgyorgy on Saturday November 21, 2020 @12:15PM (#25170950)

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.

[ Parent | on HN ]

Re:PostgREST: REST API for any Postgres database by philwelch on Saturday November 21, 2020 @04:05PM (#25172760)

REST 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

[ Parent | on HN ]

Re:PostgREST: REST API for any Postgres database by avinassh on Saturday November 21, 2020 @12:20PM (#25171001)

> 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

[ Parent | on HN ]

Re:PostgREST: REST API for any Postgres database by corytheboyd on Saturday November 21, 2020 @12:38PM (#25171149)

I 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

[ Parent | on HN ]

Re:PostgREST: REST API for any Postgres database by abraae on Saturday November 21, 2020 @01:12PM (#25171460)

To REST purists, APIs must use HATEOAS to be considered REST.

[ Parent | on HN ]

Re:PostgREST: REST API for any Postgres database by masklinn on Saturday November 21, 2020 @01:21PM (#25171558)

"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).

[ Parent | on HN ]