토론: Application caches: cache-aside, TTLs and invalidation

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

번역이 없어 원문을 표시합니다. 원문

Delete-on-write has its own race: a reader can fetch the old value from the source just before the write commits, then populate the cache after the delete, leaving stale data until the TTL expires. The article presents deletion as the safe choice; it is safer than update but not safe. Short TTLs or versioned keys that change on every write are the actual fix.