GraphQL: The Documentary

Channel:CultRepo · Length:27:57 · Published:2019-06-24 · Views:603861

Watch on YouTube

Summary

A documentary on how GraphQL came to be at Facebook, featuring its co-creators Lee Byron, Dan Schafer and Nick Schrock. It covers the problems it solved and its adoption at companies like Twitter, Airbnb and GitHub.

Why HN recommends it

HN recommends it for understanding the original motivation behind GraphQL before judging whether it fits your problem.

Listen to what the developers tell which problems they had to solve when they invented GraphQL. — HN, 2022

Web development · Software architecture & design · Tech company stories & documentaries

Subtitles (excerpt)

For those of you who don't know me, my name is Dan Schafer, I'm a software engineer at Facebook and along with Lee Byron and Nick Schrock helped to create GraphQL about seven years ago it is unreal to be here I feel like I say this every time because every time it's true you know looking around the room it was 200 people two years ago 400 people last year 800 people here in Berlin today for a GraphQL conference this doesn't happen without you the community so thank you all for coming this is GraphQL think I'm not giving anything away there I feel like at this point the story of GraphQL we've told it a bunch of times you know we've told that story of the initial prototype in February of 2012 and you know hacking in the corner and trying to figure out what this was going to be and eventually shipping it in the iOS app in August the open sourcing in July of 2015 and then of course where we are today but the story that we haven't told quite as much and the story that I think is really important to understand GraphQL and why it exists and a lot of the decisions we made is that pre-history what I'd like to talk about today is what GraphQL was before GraphQL the origin stories of GraphQL really date to

On Hacker News

Watch this Honeypot documentation about GraphQL. Listen to what the developers tell which problems they had to solve when they invented GraphQL. You likely do not have any of these problems. [VIDEO] — realPubkey, 2022-05
I recommend to watch the documentation about the facebook people that invented GraphQL [1]. Listen careful to which problems they solved with graphql, then think about the problems you have to solve for your application. Most of the time GraphQL is not worth its tradeoffs. [1] [VIDEO] — typingmonkey, 2020-07
> It is unclear that the total impact on performance would be significantly negative compared to the typical GraphQL API. Some of the problems also apply to GraphQL, people just need to constrain the query complexity in the end. But yeah, it would bite Datalog more if not designed well enough, and it's harder to tackle Datalog than to GraphQL. Other thoughts on this topic: I love GraphQL but I wo… — namelosw, 2019-12
So we invented a query language (GraphQL) to solve an orchestration problem? Sorry but I don't buy this reason. Especially not to the question: "Why we don't use SQL as a query language?" especially because REST was around way earlier than GraphQL. Your reasoning could be great to answer the question: "Why we like GraphQL where there are a lot of microservices?" BTW, there is nothing inherent in … — siscia, 2019-10
1) I think GraphQL is more relevant than ever. Facebook ran into the same problems like Netflix, Airbnb and Twitter and thus came up with GraphQL [0]. 2) The most popular one I know is GitHub's GraphQL API [1]. I made the difficult decision to rely on their API to teach GraphQL in my free book [2]. So far, there were no breaking changes for me and people love it to learn GraphQL from a client's p… — rwieruch, 2019-07

Related videos