Reimagining the frontend-backend divide thanks to GraphQL
summary
Claims that frontend teams can own the schema and speed delivery by running a GraphQL function on the client to automate data fetching and local state, using familiar libs (graphql-js, normalizer/Relay patterns versus ngrx) and then lift the same boxes to the server with minimal change. Cites a paper that UI devs spend less than a third of time on actual UI. Demonstrates replacing reducers/selectors with delete a bunch of local code automation, plus tutorials and free PRs to prove it works.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:00Why GraphQL
- 5:00What is GraphQL
- 7:00Benefits of GraphQL
- 11:30Where to use it
- 16:00Normalizer
- 20:30App Architecture
- 22:50Takeaways
- 24:30Backend developers
related talks
23mA glimpse of GraphQL" Frontend developers’ life is easy now!"
55mFront-End Independence with GraphQL and Redux
24mRethinking frontend architectures with data layers
32mGraphQL-Anywhere - How GraphQL can improve your work across all of your stack
29mWrite Queries, Not Code
30mReact state management in a GraphQL era
22mAdopt GraphQL without Writing any Backend Code
38mThe Front End Architecture Revolution