Fast Backends for Faster Frontends
summary
Shows a Remix demo that moves data work to the server: route loader/action functions run on the server, nested loaders run concurrently to avoid request waterfalls, and client UI receives pre-serialized data so components have no async state to manage. Implements a city combo box that queries a search endpoint returning the top 16 matches, uses fetcher.load for background requests, and sets cache-control: max-age=60 so repeated keystrokes hit the browser cache. Builds create and delete user actions and verifies round‑trip behavior.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:34Front-end vs back-end shifts
- 4:05Node.js and React impact
- 7:58Remix introduction
- 9:23Why Remix for speed
- 10:07Remix routes and loaders
- 13:18Live Remix demo
- 14:25File routing and layouts
- 16:54Form actions in Remix
- 26:10Progressive combo boxes
- 28:58useFetcher data fetching
- 31:04Cache control headers
- 33:07Deleting data and errors
- 36:16Fetcher forms enhancement
- 38:52Error boundaries handling
- 40:05Performance benchmarks
- 41:30Route vs component data
- 42:36Q&A
related talks
25mFast Backends for Faster Frontends with Remix
22mBringing Back Progressive Enhancement
59mRemixing Frontend Development
27mWhen To Fetch: Remixing React Router
48mReact Remixed
31mReact Server Components Elevating Speed, Interactivity, and User Experience
23mMicro-Frontends Performance and Centralised Data Caching
58mFrontin' like a Back-er