Concepts for GraphQLs
GraphQL concepts are the ideas behind the language: a single endpoint, queries that read data, mutations that change it, and responses shaped by the request. Compared with REST, the client chooses fields, which avoids over-fetching and extra round trips. This unit is the starting point for reading and writing any GraphQL operation.
Stage: Basics · Part of the GraphQL roadmap · Last reviewed 19 November 2026
What to learn in Concepts
- Write a query that selects nested fields in a single request
- Pass variables and arguments into a query instead of hard-coding values
- Write a mutation that creates a record and returns selected fields
- Explain how GraphQL over-fetching and under-fetching differ from REST behaviour
- Use fragments and aliases to avoid repeating fields
Concepts interview questions
How does GraphQL differ from REST?
REST exposes many endpoints, each returning a fixed shape. GraphQL exposes one endpoint and lets the client specify the fields it needs, often fetching related data in one round trip. REST gets simpler HTTP caching, while GraphQL gives clients more control over responses.
What is the difference between a query and a mutation?
A query reads data and should have no side effects. A mutation changes data on the server, such as creating or deleting a record. Top-level mutation fields run one after another in order, while query fields may be resolved in parallel.
Where Concepts fits in the GraphQL roadmap
Concepts belongs to the Basics stage (beginner level), which takes about 13 hours. Query language.
Other units in this stage
Back to the full GraphQL roadmap