GraphQL Under the Hood
What is GraphQL?
In order to understand how GraphQL works, we need to first have an understanding of what GraphQL is.
GraphQL has a large, quick moving community, which is great, but because of the size of the ecosystem and how fast it's growing, sometimes it's hard to understand what exactly GraphQL is and what you need (or don't need) to use it.
So, what is GraphQL?
- A Type System
- Formal language for querying data
- Rules for validating a query against the Schema
- Rules for executing a query against the Schema
What you DON'T NEED to use GraphQL
You can use GraphQL without adding anything to your client. You can use
fetch() or anything else that can make a request to a GraphQL server. You don't need Apollo or Relay. Eric emphasizes that
- GraphQL IS NOT the GraphQL Ecosystem
- GraphQL IS NOT GraphQL Implementations
GraphQL Under The Hood
A GraphQL request can be made in any way. It could come as a custom header, use protoBuf or even as a cookie!
The community has largely standardized on HTTP POST requests, but it's still up to the system to determine how to send GraphQL requests.
A (typical) Query Lifecycle
- Receive Request
- Parse Query
- Validate Query
- Execute Query
- Return Result
Parsing a GraphQL Query
Once the request is made, there's a request lifecycle.
The first thing that happens is Lexical Analysis. Much like a grade-schooler learning to de-construct a sentence and identify nouns, verbs and pronouns, GraphQL's Lexer identifies the pieces of the GraphQL query.
Validating the Query
Once the query has been parsed, it goes through a validation process to make sure the request is executable against the Schema.
This is a stage of the request that can be skipped.
Persisted Queries are pre-validated query strings stored on the server that can be executed by requesting a specific identifier connected to the intended query. Using persisted queries can reduce the upload time of requests, but can also allow for servers to bypass Lexing, Parsing and Validation and speed up execution as the queries are already known ahead of time.
While this might be right for some systems, Eric points out that this may not be the right option for everyone and may not even be possible in some server implementations.
First, GraphQL identifies all the operations. A GraphQL request can contain multiple operations.
Then it moves on to resolve each operation.
At this point, the selection set is executed.
A GraphQL server, when preparing a field of a given scalar type, must uphold the contract the scalar type describes, either by coercing the value or producing an error.
If the field in the selection set is a Scalar, GraphQL will resolve the field, otherwise it recurses until it resolves to a Scalar.
And finally, a field is resolved.
- There's plenty of opportunity for innovation with how to further optimize GraphQL requests.
- Context is widely used to store things like user identification, but it's not part of the spec
- A list of GraphQL code and resources: https://github.com/chentsulin/awesome-graphql
- The GraphQL Spec: https://facebook.github.io/graphql
- An excellent interactive tutorial: https://www.howtographql.com/
- GraphQL Demo Code: https://github.com/baer/graphql-demo
- GraphQL Demo Code in Launchpad: https://launchpad.graphql.com/nnnwvmq07