Personalized responses can break caching strategy quickly. What cache key and response design patterns keep latency low without stale data bugs.
Sarah Connor
Are you using a CDN by any chance?
Yes, but only cache shared or normalized fragments at the CDN, not full per-user responses.
Sarah
That’s the sane default, and the thing that breaks first is usually cache key sprawl once personalization leaks into headers or cookies.
Ellen
Keep the edge cache on a tiny public key and move personalization to a second step like ESI, AJAX, or signed user-context buckets, because once raw headers or cookies hit the key you lose hit rate and predictability.
Sarah
