Incremental Static Regeneration
Big and complex systems with many web pages encounter the issue of having to re-build an entire app for each deploy. Systems like this usually deal with this issue by using server side rendering and a caching layer (e.g Varnish)
Rendering and building a page by request is not a solution. Neither is building the entire app everything at once. That's why we came up with Incremental Static Generation.
This is useful for:- Big applications, with loads of pages
- Architectures that tend to rely on SSR
- Dynamic Content, content changes fast
Benefits:
- Works in the background, users always get a static response
- Pages get statically regenerated, including all changes from the CMS
- It's fully automatic, no need to trigger a full rebuild
Read more about this topic:
Up Next
Features that we are planning
- Re-generating and invalidating multiple pages at once (like your blog index and a certain blog post)
- Re-generating by listening to events (like CMS webhooks), ahead of user traffic