Making It All Fit Together with React and GraphQL
summary
Stripe uses React + GraphQL + Apollo and shows concrete pieces: a global schema file checked into the mono repo, automatic Flow type generation, a wrapper that yields ready-to-use React components from queries, and schema-based data mocking with overrides for mocks to exercise edge cases and error/loading states. CI runs a backwards-compat checker that forces deprecate-then-delete changes, and monitoring reports per-field usage so removal is safe. These tools speed testing, reduce regressions, and make rollouts safer.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:32STRIPE'S WEB STACK
- 1:44GraphQL: Define a schema instead of a list of endpoints
- 2:54PRODUCT DEVELOPMENT
- 3:43Why does GraphQL have such a big impact?
- 4:30Why mocking?
- 6:16EXAMPLE: DEFAULT MOCKS
- 6:44EXAMPLE: OVERRIDING FIELDS
- 7:06MOCK FOR LOADING/ERROR STATES
- 7:36Collaborating on an API
- 8:10Schema guard rails
- 8:47GENERATING FLOW TYPES
- 10:19How do we make breaking changes?
- 11:19Great community tools and docs
- 11:59AUTOMATICALLY GENERATE STATIC TYPES
related talks
24mBuilding Reactive GraphQL Apps With Apollo
01h 02mDesigning a Flexible UI Architecture with React and GraphQL
05mYou Don't Need a Fancy Framework to Use GraphQL with React
26mFull Stack Type Safety with React, GraphQL, and TypeScript
34mCreate Flexible React Applications Using GraphQL APIs
30mReact & GraphQL - Bringing Simplicity and Correctness to Client Side Development
35mFull-stack Type Safety with React, GraphQL, and TypeScript
22mReact State Management in a GraphQL Era
