When NOT to Use Next.js
summary
Next.js claims a hybrid architecture that lets pages be fully static, fully dynamic, or mixed per route with built‑in cache behavior so teams avoid custom caching. At HashiCorp a seven‑person team runs 14 websites on a team of seven sharing components and templates and handling thousands of pages with selective prebuild versus on‑demand generation. Good for actively maintained, scaling sites; avoid for small, rarely updated sites because framework churn creates maintenance drag.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:15Intro
- 2:33Hybrid Architecture
- 9:16Background
- 11:38Hashicorp Tools
- 15:04How Does a Team of Seven Devs Keep Up with the Scale Requirements of a Hyper Gross Startup while Maintaining and Innovating on 14 Different Websites
- 15:36Benefits of a Shared Platform
- 16:00Shared Tooling
- 22:52Why You Should Learn React Instead of Jquery
- 23:09Future of React
related talks
30mComposition, Caching, and Architecture in modern
45mNext js: Build a State of the Art E commerce in Fullstack React
27mAn introduction to Next.js and what's to come in 2021
40mHow not to fail when choosing a modern Jamstack framework
10mNext.js is all you need for a fast-growing startup
25mNext.js: Choosing an Optimal Rendering Pattern for your Application
21mWhat to expect from a modern web framework?
31mThe post-Jamstack world and the rise of Hybrid Frameworks