The time to go full stack is now
summary
A full-stack migration demonstrably speeds pages: an 80-movie demo using Next.js/Remix and React Server Components runs faster than a client-only SPA in lab tests on render.com lab tests and edge/long-running servers. Moving data fetching to the server cuts round trips to LCP from three to one, eliminates spinners, and lets the backend filter fields to avoid overfetching—saving about 12 KB on that dataset. Caching and server-side computation further improve real-world web vitals.
AI-written summary · about
chapters (7)
- 0:00Introduction and React evolution
- 1:44Why go full stack now
- 3:50Building a business case
- 5:58Full stack advantages demo
- 7:00Seven performance improvement steps
- 12:36Caching and trade-offs
- 14:42Summary and next steps
related talks
31mReact Server Components Elevating Speed, Interactivity, and User Experience
45mSPA, isomorphic and back to the server: our journey with JS
33mGo Full Stack Server-Side Rendering vs SPAs
19mMoving from a React SPA to Next
06mFullstack can be fun (again)
21mDante’s Inferno of Fullstack Development (A Brief History)
33mUniversal React Apps Using Next.js
08mLightning fast SSR React apps with top perceived performance and no (client side) JavaScript