Make us of Next.js On-Demand Revalidation.
Currently we use interval based revalidation which means pages get rebuilt if a user visits a page and a fixed interval has passed since the last page rebuild. Because of this, pages often get rebuilt even if they haven't changed. This results in unnecessary API requests and CPU usage on the server.
To reduce this, we can make use of On-Demand Revalidation, an experimental feature of Next.js. This way pages only get rebuilt, if the back-end (our database editing tool, Nova) sends a request to the client. How this will work needs to be planned in detail. We need to be careful to not have any blind spots (pages that don't get rebuilt at all).
See also: AnimeThemes/animethemes-server#364
Make us of Next.js On-Demand Revalidation.
Currently we use interval based revalidation which means pages get rebuilt if a user visits a page and a fixed interval has passed since the last page rebuild. Because of this, pages often get rebuilt even if they haven't changed. This results in unnecessary API requests and CPU usage on the server.
To reduce this, we can make use of On-Demand Revalidation, an experimental feature of Next.js. This way pages only get rebuilt, if the back-end (our database editing tool, Nova) sends a request to the client. How this will work needs to be planned in detail. We need to be careful to not have any blind spots (pages that don't get rebuilt at all).
See also: AnimeThemes/animethemes-server#364