Hacker News Reader

Comment by guyromm | Hacker News Reader

postgREST is the bomb and, together with svelte, changed my life, productivity wise - no less.

here's a short video explaining how this project can allow a front-end developer unleash PostgreSQL's power without having to write backend code.

https://drive.google.com/file/d/1ncp00Mb7L3TO9TIRgNEF6pRdt-b...

View on HN

If you use this, also take a look at GraphQL, AWS has a hosted GraphQL service called Appsync, and if you look into self hosted you can also use Prisma.

Imagine postgREST with a better query format.

Checkout postgraphile at https://www.graphile.org/ , they have a whole ecosystem build around postgresql, typescript, graphql.

Just to +1 this and add that maintainer responsiveness and its community is excellent.

Just curious, how does it compare to Hasura? Looks pretty similar but without the ui

Someone called it: "hasura for adults”

It's highly customisable, works directly with postgresql row levels security and the performance is quite good. It has a custom GraphiQL gui to work on queries/mutations.

To really see how it all works together checkout the starter project: https://github.com/graphile/starter it has migrations, job queue, graphql-codegen etc.

Benjie (https://github.com/benjie) is one of the greatest maintainers I've ever seen!

tried GraphQL, not sure I'm sold on it viability. Sure it is very uniformed, however for nested queries it is very slow. We already have SQL don't need another querying language in js. If I really want get fancy then prolog would be much more preferred. On top of that FB is backing the project make me feel very uneasy, the same exact reason why I won't want to use React with a 10 foot pole.

As far as I know, AppSync doesnt provide GraphQL resolver on top of an RDS out of the box, one needs to write these resolvers by hand.

Or am I missing something?

(disclaimer: not feeling totally authoritative on this, have not used graphql in production).

i feel that the choice between postgrest & postgraphile / another graphql solution revolves around whether you're a front-end dev who doesn't get to arbitrarily change/expose data schema. if this is true, and you are collaborating with other devs on the code then the added flexibility in querying probably outweighs the inferred complexity of this complex data abstraction.

if, however, you control both back and front-end, graphql isn't really needed, as you can expose whatever views you fancy by means of SQL (via views, table/row permissions, rpc functions exposed by postgrest, etc)

Excellent video. Any reason for sharing with drive instead of YouTube?

thank you! am still waiting to see if/when it'd feature on svelte fall summit before "properly" posting it.

btw. i've also done on a step-by-step "sample app" tutorial for svelte+postgrest. i'd say its still a little rough: https://www.webgma.co.il/Tech/

Good video, thanks. Makes me feel like I'm going in the right direction with this stack as a front-end guy.

Reply on news.ycombinator.com