4 ms·
* in my experience you basically have to write every call anyway, in other words, getting GraphQL set up on the backend is at least as much work as writing API
by throw1234651234 4y ago
* in my experience you basically have to write every call anyway, in other words, getting GraphQL set up on the backend is at least as much work as writing API boilerplate. Again, correct me if I am wrong. It's been a while since I last used GraphQL and I keep hearing about hearing about magic libraries that make it "effortless".
- belmont_sup 4y agoI abstain from writing graphql apis now because they’re too much work for me when toy apps are simple and I can render json. But if a team does want graphql without the fuss of openapi, json schemas, and swagger docs, I recommend tools like Hasura that autogenerates graphql apis over my db. Auto generation of graphql resolvers are the way to go for productivity. Supabase even created a Postgres extension to perform graphql directly within postgres https://supabase.com/blog/2021/12/03/pg-graphql https://supabase.com/blog/2021/12/03/pg-graphql
- throw1234651234 4y agoThanks for the info!