Most Next.js performance guides stop at "use the built-in cache". That works until you deploy several instances, run on a serverless platform where the file system is ephemeral, or need to invalidate a specific product page 200 milliseconds after a mutation. That is...








