Cascading cache invalidation ↦
Turns out one of our asset caching best practices (content hashes in filenames + far-future expiry) has a serious flaws in it:
In practice, changes to one of your source files almost always invalidates more than one of your output files—and this happens because you’ve added revision hashes to your filenames.
Philip goes on to explain why this happens and then proposes 3 possible solutions. Good stuff 👌
Sign in or Join to comment or subscribe