Marketing pages, a CMS blog, tenant storefronts and a logged-in app — all on one domain, for two completely different reasons. The Cloudflare, Nitro and i18n config that decision cost us, and the four bugs we only found by reading response headers.
Every page we serve falls into one of four buckets, and they want opposite things from a cache:
Marketing pages never change between deploys.
Blog articles change when someone hits publish in the CMS.
Tenant storefronts change when a seller edits a product — and must never be cached for the seller themselves.
The logged-in app must never be cached at all.
> TL;DR — I run four different domains off one Next.js codebase: a marketing site at...
Four cache layers sit between your user and your database. Most teams use two. Here's where each layer wins and how to stop them…
Sentry replaced its CMS with Astro, Markdown, and Claude Code skills — cutting build times from 14 to under 4 minutes and…
by Rashed We shipped an auth bandaid at 2am. Cookies wouldn't flow between platform.ginilab.com and...
We added a cache-first design to the cross-site updates dashboard, then wired the site-list badge to...
The Quest Begins (The "Why") I still remember the night our API started to cough. A flash...
