Fun fact
GraphQL was born at Facebook in 2012, where mobile engineers fought REST endpoints that forced the app to download far more data than a screen needed - or demanded several round-trips to assemble one view. The answer was radical: let the client describe the exact shape of the data, and the server returns exactly that, nothing more. Facebook open-sourced the specification in 2015, and in 2018 stewardship moved to the newly created GraphQL Foundation under the Linux Foundation. The Schema Definition Language officially joined the specification on February 9, 2018. Today GitHub, Shopify and Yelp all expose public GraphQL APIs. One elegant detail: every field is nullable by default, and a single exclamation mark is all it takes to make one required.
What is overfetching and why does it matter
Overfetching is what happens when an API hands back more data than the screen will ever show - a full object where the client needs three fields, or a list that arrives bloated and gets trimmed on arrival. The wasted bytes cost real money on mobile networks: slower loads, drained batteries, bigger data bills. The mirror problem, underfetching, forces an app to chain several round-trips just to assemble one view. REST can only soften both pains with hand-made endpoints and field filters; GraphQL removes the mismatch structurally by letting the query itself declare exactly which fields the server should return - and by returning precisely that, nothing more.
Tool usage guide
- Paste your GraphQL query into the editor - the formatter straightens out messy indentation automatically.
- Load a schema in SDL format and explore its types, fields and relations in the visualizer.
- Assemble or edit the query by picking fields; the builder keeps the syntax valid as you go.
- Copy the finished query, run it against your endpoint, or share it with the team.