GraphQL as a Data Layer for Your UI
summary
Explains how to get a production GraphQL data layer without backend changes by using Stepsen to combine REST, databases or other GraphQL sources into one endpoint, demoing a developer portfolio that pulls Dev.to, GitHub and Twitter, returns mock data for quick work, and then downloads schema files to run and deploy locally with GraphQL Studio. Shows custom directives for REST/DB/graphql connectors, explains caching and error aggregation, and warns that resolvers are not endpoints so backend optimizations are required.
AI-written summary · about
chapters (20)
- 0:00Introduction to GraphQL
- 1:06Why GraphQL as a data layer
- 2:31What is GraphQL
- 5:20GraphQL key features
- 7:25GraphQL vs REST
- 8:06Transforming REST to GraphQL
- 9:30Introducing StepZen
- 10:53Demo GraphQL Studio
- 14:41Using GraphQL in a JAMstack app
- 17:51Local GraphQL API setup
- 22:23Resources and examples
- 23:06Poll results and Q&A intro
- 23:49Transitioning from REST to GraphQL
- 27:24Handling errors and availability
- 29:32Decorating API content
- 31:16Self-documenting APIs
- 34:27GraphQL auto-completion
- 35:48Understanding GraphQL directives
- 39:00Learning GraphQL resources
- 41:03Closing and Q&A summary
related talks
21mLet's Talk GraphQL With Your Services
26mSponsored Session: From Prototype to Production: Building Custom GraphQL APIs
23mGradually Adopt GraphQL Without Writing any Backend Code
28mGraphQL without GraphQL - Backend Agnostic GraphQL inspired Queries For Colocating Data Requests With Components
08mWhen (Not) To Create A GraphQL Server
16mIntro to GraphQL
23mBlueprints of Successful GraphQL Architectures
55mGraphQL - APIs the New Way