3 ms·
I'm a big fan of postgrest (https://github.com/begriffs/postgrest/ https://github.com/begriffs/postgrest/). It creates a RESTful HTTP API out of your existing
by daurnimator 10y ago
I'm a big fan of postgrest (https://github.com/begriffs/postgrest/ https://github.com/begriffs/postgrest/).
It creates a RESTful HTTP API out of your existing postgres schema. It practically eliminates the need to write a CRUD backend.
- ruslan_talpa 10y agoUsually when you say CRUD people tend to think "limited functionality" and PostgREST is a bit more then "basic CRUD" as i am sure you know. It's interface is powerful enough to support GraphQL on top (since this is the topic of this thread :) https://subzero.cloud/ https://subzero.cloud/ )
- brandur 10y agoYes, PostgREST is awesome :) It turns out that most of what is usually expressed in implementation code assuming that you're hitting a dumb backend is just as well-served by SQL functions and schemas. This probably breaks down for larger projects, but it certainly has its place, and I can imagine something very similar be done for GraphQL.
- ruslan_talpa 10y agoI don't think it breaks down (as long as most of the data comes form the database). For example i know exactly how paymoapp.com (similar to basecamp) is structured , i consider it to be a fairly large system and i know for a fact that PostgREST can support that. As for the "very similar be done for GraphQL", there is https://github.com/postgraphql/postgraphql https://github.com/postgraphql/postgraphql which was based on postgrest ideas. Another approach would be to build graphql on top of postgrest (my comment below)