David Novicki
At it's simplest form, asking for fields on objects. Think of queries as refined GET methods
This includes nested objects or arrays as well as the ability to chain multiple queries in parallel
And further more, we can add arguments to our queries
Just like most query languages, we are able to add inline logic to our query through GraphQL directives and variables
Think as mutations as the POST of GraphQL
Mutations allow the ability to run queries upon completion so you can execute POST then GET functionality in a single request
Multiple mutations will always run in series rather than parallel as to avoid side-effects
Schemas are the glue/mapping for our query language to business logic
They define a general outline of abilities and provide a validation layer to all incoming queries and mutations
The foundation for queries and mutations to all your custom business logic. All queries and mutations must have a corresponding resolvers
Pros:
Cons:
Pros:
Cons:
GET: /authors/:id
GET: /authors/:id/posts
GET: /authors/:id/posts/:id/
GraphQL
REST
Returns all data resulting in large response sizes
GraphQL
REST
Features
Features
Features
Continuing Resources