An open-data catalog can tolerate roughly two minutes of cache staleness, but election-night results pages need near-zero stale cache. How should cache TTLs be set?
Select an answer to reveal the explanation.
Short Explanation
Not every city page ages the same—open-data can nap for a couple minutes; election night can't. Set TTLs to match freshness needs instead of one blunt dial. Right TTL, right page, happier citizens.
Full Explanation
Cache TTLs must reflect freshness requirements: relatively stable open-data catalog content can use multi-minute TTLs, while election-night results typically need near-zero TTL or cache bypass. A single long TTL, inverted settings, or blanket disables fail either performance or correctness. Tuning TTL versus freshness is a Domain 4 caching skill.