SSR & SSG in NextJS
summary
Converts a client-side fetch into getServerSideProps then into getStaticProps & getStaticPaths with a demo that initially generates ~100 pages then switches to prebuilding three popular pages and creating others on first request, exposes build time pain when pages scale, uses fallback: true and revalidate / ISR so stale pages regenerate, and shows the site serving prebuilt pages quickly while on-demand page generation works and lands in the server for future requests.
AI-written summary · about
chapters (12)
- 0:00Removing customer friction
- 1:31Client-side limits
- 2:55Switching to SSR in Next.js
- 5:45Limitations of server-side rendering
- 6:28Introducing SSG in Next.js
- 12:14Static pages with getStaticPaths
- 13:59Large-scale static generation
- 17:42SSR vs SSG demo
- 18:24Q&A on incremental static regeneration
- 20:11Q&A on page priority
- 22:00SSR vs SSG for business
- 25:10Migrating legacy to Next.js
related talks
30m50 shades of React rendering with Next.js
20mNext js CSR, SSR, and SSG
44mServer Side Rendering from the trenches
20mCSR, SSR, SSG, ISR, and OMG. WTF? BBQ!
25mNext.js: Choosing an Optimal Rendering Pattern for your Application
20mAdvanced Rendering Patterns
12mReact Server Components and SSR: How it Fits
30mServer Side Rendering: Scared Eyes, Working Hands