How not to fail when choosing a modern Jamstack framework
summary
A company migrates from Gatsby to Next.js after discovering Gatsby’s long builds and brittle page/data model: site has about 1,000 pages and ~2.5 API queries per page, previews force 25 minute rebuilds so editors wait 25 minutes vs 3 minutes build, and complex getNodes templates become unmaintainable. The new stack uses Next.js ISR and server-rendered previews, TypeScript-generated content models, API routes and serverless functions, and moves hosting off Azure toward Next.js-friendly deployment and incremental builds.
AI-written summary · about
chapters (4)
- 0:00Start
- 11:34Better site performance
- 35:33Was it worth the effort?
- 37:37Should you always use Next.js then?
