Caching in Next.js 13

What would you do in case of a headless CMS? We can safely assume that it won't be changed often (weeks or months bween updates) but if it happens, it needs to be updated instantly. Or better stick to using webhooks?

In this case, I'd keep it static and redeploy after content updates. Redeployment invalidates the cache. Alternatively, we can set an API route that revalidates a particular tag or path and trigger it after every content update.

What am I doing wrong?

Try deploying it to see how it works with the actual cache.

Awesome features. Loved it

Banger video as always Alex!

@jonathan_wilke didn’t you had some caching trouble ? Maybe here is something helpful

Loving this content. Removing complexity and making it digestible and understandable.

probably the easiest to understand caching explanation for nextjs i've seen

straight to the point and informative!