Front-End Independence with GraphQL and Redux
summary
Presents an architectural model using GraphQL and Redux to decouple application domain logic from front-end technology, so the UI can evolve without forcing domain refactors. Shows case studies of migrating from a coupled RESTful setup to a decoupled architecture that unifies mobile and web API calls, and discusses benefits, side effects, and cultural changes from adopting this approach.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:48Modern front-end evolution
- 12:15What is GraphQL
- 20:09Traditional API problems
- 27:21GraphQL schema and types
- 33:59State management with Redux
- 39:21Redux architecture and flow
- 46:01Strategy benefits
- 47:50Q&A
related talks
31mReimagining the frontend-backend divide thanks to GraphQL
25mReact state management in a GraphQL era
52mState management in a GraphQL era
45mDomain-Driven Design in Micro Frontends
27mReact State Management In a GraphQL Era
23mA glimpse of GraphQL" Frontend developers’ life is easy now!"
30mReact state management in a GraphQL era
01h 02mDesigning a Flexible UI Architecture with React and GraphQL
