Server
GraphQL's server side setup has following important components:
typeDefs - Type definitions aka schema of your data models and shapes/contract defs of your queries and mutations. (Think of Queries and Mutations as your GraphQL server's endpoints. Queries are for GET, Mutations can be for PUT or POST.)
resolvers - functions/code for your queries and mutations. These function signature should match with the signature that you have defined in your queries/mutations schema. In these functions, you write code for how or where to get or post data, and then resolve/customize/massage the response data as defined in the typeDefs of data models. ( for example a resolve function could contain a MongoDB/Mongoose find statement to query some data or even could be an Axios call to query some external REST API endpoint)
TypeDefs / Schema
type definitions of data models, queries and mutations:
are written in GraphQL Schema Language.
are first written in a templated string format (within a pair of backticks (`...`)
Resolvers
Make Executable Schema
Once you have typeDefs and Resolvers set up, you make a executable schema that GraphQL can execute using the graphql-tools's
makeExecutableSchema
function:
Set up Express to use graphQLExpress middleware
Once we have our executable schema ready, we can provide it to graphQLExpress to set it as a middleware for our node Express server:
This is server side setup for GraphQL in brief. Next we'll set the client side setup needed for GraphQL
Last updated