3 ms·
Do we need GraphQL? https://kellysutton.com/2017/01/02/do-we-need-graphql.html https://kellysutton.com/2017/01/02/do-we-need-graphql.html (Disclaimer: From my
by kellysutton 8y ago
Do we need GraphQL? https://kellysutton.com/2017/01/02/do-we-need-graphql.html https://kellysutton.com/2017/01/02/do-we-need-graphql.html
(Disclaimer: From my personal blog)
- acjohnson55 8y agoThe problems you outline are real, but have straightforward solutions. You can persist queries to the server and then GET them in a really natural way, using query params to provide arguments for your GraphQL query's variables. Then, when it comes to caching, just do it at the resolver level, using something like DataLoader, perhaps with a KV store.
- lolive 8y agoFor the Semantic Web, I developped a query repository and a query builder GUI (cf datao.net). And my frontend (search.datao.net) fetches thoses queries and apply them upon resource IDs it receives from a search engine.