Why You Should Use Implementation-First to Build Your GraphQL Schema

on YouTube ↗29m

" summary

Implementation-first claims that the GraphQL schema infers GraphQL schema from code so types and resolvers live in one place, removing duplicated SDL, generated types, and separate resolvers. Concrete tools shown: Strawberry (Python), Hot Chocolate (.NET), Grats (TypeScript) and Facebook’s Hack server; features demonstrated include language generics and Strawberry’s field extensions. This approach ships in production since 2016/2019, reduces runtime type mismatches, and is type-safe by design.

AI-written summary · about

" chapters (10)

1. 0:00Introduction
2. 0:44Schema first vs code first
3. 7:02Implementation first concept
4. 10:11Frameworks using implementation first
5. 13:44Strawberry implementation example
6. 15:49Thinking implementation first
7. 17:14Advanced patterns in implementation first
8. 20:24Why use implementation first
9. 21:46Credits and resources
10. 22:51Q&A session

" related talks

• 27mThe Benefits of Code First Over Schema First in GraphQLPatrick Arminio · GraphQLConf 2023
• 48mGraphQL - a type system for your APIOleg Ilyenko · Scala Days Copenhagen 2017
• 25mGraph-First Services Using GraphQLAdam Crane · Scale By The Bay 2018
• 32mFrom learning to thinking in GraphQLGlenn Reyes · FrontEnd Con 2018
• 41mGraphQL: The Good PartsSerhii Lishchuk · .NET fwdays'24
• 08mWhen (Not) To Create A GraphQL ServerRoy Derks · GraphQL Galaxy 2021
• 24mGoing GraphQLChris Biscardi · Gopherpalooza 2018
• 18mWelcome to GraphQLJesse Martin · apidays Paris 2021