Skip to content

Instantly share code, notes, and snippets.

@colmarius
Last active March 28, 2019 21:55
Show Gist options
  • Save colmarius/4e097c07acb41f8a56319a01fa7ba4f1 to your computer and use it in GitHub Desktop.
Save colmarius/4e097c07acb41f8a56319a01fa7ba4f1 to your computer and use it in GitHub Desktop.
Intro to GraphQL: https://bit.ly/2HIzTw1

Intro to GraphQL

Wait...

What are the problems with REST?

What is GraphQL?

  • enables declarative data fetching

  • a GraphQL server exposes a single endpoint

  • it is a query language for APIs

Advantages of GraphQL vs REST

Who is using GraphQL?

Why GitHub is using GraphQL

GitHub chose GraphQL for our API v4 because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want—and only the data you want—is a powerful advantage over the REST API v3 endpoints.

Github v4 note

Types, Fields and Resolvers

Queries and Mutations

Schemas and Types

Schemas and Types

Can you think about the benefits of having Schemas and Types?

GraphQL in Practice

Resources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment