DEV Community

Discussion on: Incremental Static Regeneration: Its Benefits and Its Flaws

Collapse
 
rogerbramon profile image
Roger Bramon • Edited

Nice article Cassidy!
We are currently in the process of moving our e-commerce websites to Jamstack using Netlify.
The main issue we are encountering is build time because we have a product catalog of thousands of pages. Info there is pretty much static and rarely changes because dynamic data like prices is fetched client side. Thus, having ISR would allow us to deploy a new version fast building only the most popular product pages while the rest are being built and updated on demand.

We agree on the drawbacks. However, serving a stale version on our case is very much acceptable because it's very likely that the fresh version is exactly the same and we could take advantage of a very low TTFB.

Thus, could be that without ISR we cannot move to that architecture.

Hope our use case is useful.

Collapse
 
cassidoo profile image
Cassidy Williams

Your use case makes sense! It's a very real problem. We're hoping that some of our upcoming solutions can get rid of some of the footguns we've seen (that I talked about here) so that folks like you can have the much shorter build times, without the caching issues.