Rethinking frontend architectures with data layers

on YouTube ↗24m

" summary

Argues that react server components plus GraphQL eliminate extra server-to-API network hops by running queries in-process, reducing waterfalls and security surface; claims teams past ~10 engineers benefit and cites “about 80/20” of client data needing aggregation/transformation. Shows open‑source fuse (Fuse.js) that generates a GraphQL layer, adds /api/fuse, and demos npm/pnpm setup. Demonstrates running queries with await execute inside server components (no network call) and a working live demo.

AI-written summary · about

" chapters (6)

1. 0:00Introduction and motivation
2. 3:10React server components challenges
3. 7:28Why GraphQL fits server components
4. 10:58Fragment composition benefits
5. 15:33Live demo setup
6. 22:40Demo execution and summary

" related talks

• 38mThe Front End Architecture RevolutionDavid Nolen · GOTO Chicago 2015
• 31mReimagining the frontend-backend divide thanks to GraphQLUri Goldshtein · ngVikings 2019
• 28mRequiem for APIs - The Evolution of Web DevelopmentCiprian Caba · revo.js 2023
• 20mColocating & Composing Data Dependencies with FragmentsAustin Chauncey · GraphQL Summit 2023
• 18mIs a GraphQL BFF Necessary in a Server Side React World (RSC, SAs)?Tanmai Gopal · GraphQLConf 2023
• 23mMicro-Frontends Performance and Centralised Data CachingRuben Casas · React Advanced 2021
• 45mReact Server Components: Fad or Real Progress?Thomas Simonnet · Devoxx France 2024
• 31mReact Server Components Elevating Speed, Interactivity, and User ExperienceAurora Walberg Scharff · React Paris 2025