Lee Byron - Exploring GraphQL at react-europe 2015
Why Stack Overflow recommends it
Stack Overflow users link it as one of the original talks introducing GraphQL, both for newcomers asking what GraphQL is for and as a reference when GraphQL support is discussed.
Recommended by 1 people across 1 different months, 2015 to 2017.
What it is
Lee Byron of Facebook gives a conference talk at React Europe 2015 that goes deeper into GraphQL, the data fetching language that lets clients declaratively state what data they need. He covers its core principles, how it works, and what makes it a useful tool.
What people said
Recommends Andrew Ingram · 2017-07 · Stack Overflow · on “GraphQL not for public API”
Whether it's overkill is more a matter of scale and effort than anything else. To directly address your first question, GraphQL was specifically designed for "regular applications" rather than public APIs - its use for the latter is a relatively new thing being pioneered by the community rather than GraphQL's creators. Rather than repeating answers that already exist in numerous forms in numerous places, I'm going to suggest you watch some of the original talks introducing GraphQL to the world, these are what got the early adopters excited, and should answer a lot of questions: Data fetching for React applications at Facebook [LINK] Lee Byron - Exploring GraphQL [this video]
Cites Alexander Kozlovsky · 2015-11 · Stack Overflow · on “How do I load data in many-to-many relation using pony orm?”
Thanks for the kind words! :) The problem with unnecessary ropes is that they are (1) clutter API, (2) may prevent adding useful features in the future, and (3) take time to implement them, which can be used on adding useful features instead. As an example of useful feature, we want to add GraphQL [this video] support in order to make PonyORM the main Python backend for ReactJS applications. GraphQL will allow as to take query optimization to the entirely different level, by analyzing not just individual queries, but a bunch of related queries issued together.
Cites Calebmer · 2016-04 · Stack Overflow · on “Concepts of GraphQL and Relay”
Pagination is never an easy question and not one explicitly solved by GraphQL. GraphQL provides a data fetching framework, how that framework is used to do things (like pagination) is up to the developer. The Relay [LINK] team has attempted to standardize pagination with the cursor connection specification [LINK] for GraphQL. The cursor connection specification is not unique to Relay and can be used with Angular, the main goal of the specification is to provide a standardized way to work with large collections from a GraphQL server. The main thing to note about this specification is that with every object there is an associated cursor. This associated cursor allows the client to resume pagin