The GraphQL query language can fix this overfetching problem, by allowing for unnecessary information to be ignored much earlier.
There are other things GraphQL is good at, including bundling requests into a single API call, and in streamlining type checking.
But the purpose of GraphQL, the core idea, is that it is possible for servers to be more dynamic in asking a server for information.
GraphQL started at Facebook, and has spread to replace RESTful database calls at companies like The New York Times, Twitter, and GitHub.
GraphQuill is a young, incremental product, that solves a specific problem for a specific subset of GraphQL users, just like GraphQL itself solves a set of specific problems for software engineers.

Comments to: GraphQL, GraphQuill, and You

Your email address will not be published. Required fields are marked *

Attach images - Only PNG, JPG, JPEG and GIF are supported.


Welcome to Typer

Brief and amiable onboarding is the first thing a new user sees in the theme.
Join Typer
Registration is closed.