91–94 of 94 posts
Earlier quoted context omitted.
This is entirely incorrect. GraphQL is a wrapper around your service layer, or worse, around a number of ad hoc data sources. That service layer or those data sources may query SPARQL services.
So GraphQL is a graph abstraction over REST APIs, at the cost of massive REST calls to rebuild a graph. True?
Earlier quoted context omitted.
That doesn't touch upon the N + 1 query problem at all.
Can you tell me which particular problem you're talking about? When people talk about GraphQL and the n+1 problem, they're typically talking about the problem which Dataloader solves, and this is the problem this article builds upon.
Lots of "hello world" stuff out there.
Throw in the requirements of a real SaaS and everyone shrugs.
Earlier quoted context omitted.
So GraphQL is a graph abstraction over REST APIs, at the cost of massive REST calls to rebuild a graph. True?
basically yes: http://graphql.org/blog/rest-api-graphql-wrapper/