ISR Problem: Polling( periodic revalidation) is not good solution : better solution is web hook trigger #32911
Replies: 4 comments
-
Beta Was this translation helpful? Give feedback.
0 replies
-
you should implement generate as we demand not periodically |
Beta Was this translation helpful? Give feedback.
0 replies
-
why you are quiet |
Beta Was this translation helpful? Give feedback.
0 replies
-
Please continue the conversation on the RFC: #11552 (comment) Thank you! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
suppose we have a e-commerce website and product page.. admin generate or update some field of product like price some days ...
but nextjs has to periodically fetch products for all pages created because number of user for seeing that product is something like 1k per min or more...this cause nextjs requests extra and redundant in order to find updates but there is no update per user request in revalidation ...
solution:
nextjs(nextjs sever) must not fetch to get updates for page.. it should have a api route(webbooks) to be able call by CMS to make aware nextjs to update which pages. it is efficient solution to prevent huge useless request to update.....
if u can not understand this new model, i am here to listen and explain more
thank you to let us have better web
Beta Was this translation helpful? Give feedback.
All reactions