Skip to content
Hallway
0:00 / 0:00

#graphql#github#restapi

Implementing and Using GraphQL at GitHub - GitHub Universe 2016

GitHub

704K subscribers • 8 videos on Hallway

YouTube
  • Recommended by 2 people: 1 in engineering communities and 1 curated list.
  • Presented by Kyle Daigle, GitHub & Dan Schafer, Facebook
  • May be out of date. Uploaded 10 years ago, in an area where tools change fast.

Intermediate. Assumes working knowledge.

38K views10 years ago2 recommendations

Web developmentSoftware designAPI designHTTP, REST and GraphQL

Dan Schafer and Kyle Daigle explain why Facebook created GraphQL and how GitHub implemented it for their public API.

With the GitHub GraphQL API, GitHub is creating a new way of exposing our data for integrators and our own engineers at GitHub. GraphQL works very differently than our REST API's and the GitHub GraphQL API has the added benefit of being the same platform GitHub Engineers are beginning to use. In this session, Dan Schafer from Facebook and one of the co-creators of GraphQL will start by explaining why Facebook created GraphQL, how it works, and what types of problems it solves. Then, Kyle Daigle from GitHub will share how GitHub has implemented GraphQL, how we're using GraphQL internally, and the changes we're making as an organization to support this new GraphQL API. About GitHub Universe: GitHub Universe is a two-day conference dedicated to the creativity and curiosity of the largest software community in the world. Sessions cover topics from team culture to open source software across industries and technologies. For more information on GitHub Universe, check the website: githubuniverse.com

Why it's here

2 people recommend this

What people say. Recommended as a great case study for transitioning from REST to GraphQL.

programming-talkscurated list on GitHubRecommends

Under “Web Development”

Implementing and Using GraphQL at GitHub 00:38:55 by **Kyle Daigle & Dan Schafer** (2016)
View the list

u/Aurelsicokoin r/node • Recommends

On “State of Node API Paradigms & Tooling 2016 - GraphQL vs Falcor vs REST vs ?”

REST API is still the most used paradigm but I think that GraphQL is the way to go. It provides some great features such as caching, retrieve only what you need, a strongly-typed schema . However, GraphQL is only an awesome tool for retrieve data, IMO. Having both paradigms such as GraphQL for pulling your data, and REST for mutating is not foolish. I really like the use case of GitHub and why they have chosen GraphQL for their new API (link to this video
2View on Reddit