Fast Backends for Faster Frontends with Remix
summary
Claim: Remix moves backend patterns into route files so UI and data live together. It shows loaders run server‑side per GET and return standard Response objects, nested loaders run in parallel so independent queries can be Promise.all sped up, and defer streams slow parts like comments using React 18 suspense. Actions provide route‑level POST/PUT/DELETE mutation handlers, loaders/actions cancel stale requests by default, and teams report using Remix on real sites like shopify.com.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:07Front-end and back-end connection
- 2:51Front-end evolution
- 5:16UX beyond UI
- 7:41Node.js blurred lines
- 9:45React’s impact on frameworks
- 11:08Introducing Remix
- 12:33Remix back-end performance
- 15:45Route loaders and server control
- 17:50Nested routes and parallel fetching
- 19:56Co-location of logic
- 21:42Streaming UI with deferred data
- 22:44Mutations with Remix actions
- 23:46Race conditions and cancellations
- 24:27Q&A
related talks
43mFast Backends for Faster Frontends
14mRemix run - new kid on the block, and is it a competition for Next.js and Gatsby?
28mUsing Remix, the wrong ? way
26mThe Ultimate Full Stack Framework for 2024: Remix
55mUse the Platform With Framework Agnostic Routing
45mRemix: the Truly Full-Stack Framework
40mThe Remix Evolution: How React Router v7 Enables Fast and Resilient Apps
27mWhen To Fetch: Remixing React Router