Skip to content
Hallway
0:00 / 0:00

#graphql#facebook#apigateway

GraphQL: The Documentary

CultRepo

425K subscribers • 11 videos on Hallway

YouTube
  • Recommended by 2 people: 2 on Hacker News.
  • May be out of date. Uploaded 7 years ago, in an area where tools change fast.

Beginner. No background in the topic needed.

603K views7 years ago2 recommendations

Web developmentSoftware designAPI designHTTP, REST and GraphQLHistory of computing

Co-creators Lee Byron, Dan Schafer, and Nick Schrock share the story of how GraphQL was created at Facebook and its global adoption.

The GraphQL Documentary 🚀🚀🚀 Starring Lee Byron, Dan Schafer and Nick Schrock (co-creators of GraphQL) and other big names from the #GraphQL community, "GraphQL: The Documentary" explores the story of why and how GraphQL came to be and the impact it's having on big #tech companies worldwide, including Facebook, Twitter, Airbnb and Github. Check out the home for untold developer stories around open source, careers and all the other cool stuff developers are doing at bit.ly/3nQNpBo "We have been really involved with the GraphQL community since founding Honeypot. We run the GraphQL Conf here in Berlin with Prisma, so having the chance to work with Lee, Nick and Dan to make this documentary was really rewarding." Emma Tracey, Co-Founder @Honeypot 🍯 Music: "Harper" by Neon Ridge "Revelations - Alternative Version" by Tristan Barton "The End" by Max Herve "Two States of Minds" by Max Herve "6" by Lex Villena, soundcloud.com/lexvillena/six "Til the End" by FVMELESS "Where We're Going" by Kevin Graham "Discovery" by Kevin Graham "Curiosity" by Kevin Graham "Flowing Air" by Vlad Morleo 🎥 Subscribe to our channel for future documentaries! bit.ly/31Q7wm6 Learn more about Honeypot: honeypot.io/?utm_source=youtube Follow us! Twitter: twitter.com/honeypotio Facebook: facebook.com/Honeypotio/ Linkedin: linkedin.com/company/10210811/ Instagram: instagram.com/honeypot.cult/

Why it's here

2 people recommend this

What people say. Recommended as an insightful look into the specific engineering problems GraphQL was designed to solve and why it might not fit every project.

typingmonkeyon Hacker News • Recommends

On “GraphQL Query Generator”

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 link to this video
View on Hacker News

realPubkeyon Hacker News • Recommends

On “GraphQL Is a Trap?”

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. link to this video
View on Hacker News

rwieruchon Hacker News • Mentions

On “Ask HN: Is GraphQL still relevant?”

…, ... 3 4) Using it in personal projects and one client of mine is using it in one application to aggregate multiple microservices (each one speaking GraphQL) into one GraphQL API gateway. So far, everything works like expected. We didn't hit any rate limiting and caching issues because of the N+1 problem yet. But we are prepared for them :) 0 link to this video 1 link 2 link 3 link…
View on Hacker News

sisciaon Hacker News • Mentions

On “Why Graphiti?”

…neer at facebook was annoyed by SQL, and decide to re-invent it. And that we are all following him or she just because they worked at facebook, which seems unwise. Maybe the use of types? But what is the difference between a type and something that belong to a table? Anyway, I am looking now at GraphQL: The Documentary (Official Release)1 1: link to this video…
View on Hacker News

nameloswon Hacker News • Mentions

On “Ask HN: Why GraphQL APIs but no Datalog APIs?”

> 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 would love Datalog more if the toolchain is as good as GraphQL. There's a spectrum on API of simplicity and power -- on the left, there is HTTP/REST which could be seen as a primitive/naive way of describing API it's not consumer-driven at all. On the right there's Datalog which is a powerful way of de…
View on Hacker News