Next.js is our main go to for big apps that have thousands of pages with rich content or plans to scale too. Next.js has multiple built-in configurations – automatic code splitting, file-system routing, server-side rendering with Node.js, static files exporting, and styling solutions. Arguably its main benefit is its Node.js based server-side rendering which allows your app to render on the fly appose to waiting for your site to rebuild every time you publish content like most static site generators. Instead it reloads the page when it detects any content changes.
Other benefits include blazing fast performance, higher security thanks to a decoupled headless CMS approach, SEO-friendly websites and modular design with reusable React.js based components.
If you have lots of content or if you expect your content to grow a massively over time, then static generated web pages might not be the best solution for you. The reason is, when creating a very large app with thousands of pages it can become really slow to rebuild. And if you have to wait 20 minutes when you hit publish before it goes live it’s not a very good end solution. This is where Next.js becomes the better option and really shins with its Node.js based server-side rendering.