Cache made consistent: Meta’s cache invalidation solution

Re:Cache made consistent: Meta’s cache invalidation solution by simonw on Wednesday June 08, 2022 @04:03PM (#31673218)

Is your argument here that cache invalidation may no longer be hard because you can implement systems like Polaris which continually test your cache implementation to try and catch invalidation problems so you can then go and fix them?

EDIT: Already answered in this reply: https://news.ycombinator.com/item?id=31671794

[ Parent | on HN ]

Re:Cache made consistent: Meta’s cache invalidation solution by uvdn7 on Wednesday June 08, 2022 @04:09PM (#31673284)

Polaris is actually fairly simple to build. The harder question to answer is "why cache is inconsistent" and how you debug. The second half of the post talks about consistency tracing, which tracks all cache data state mutations.

Distributed systems are state machines, with consistency tracing keeping track of all the state transitions, debugging cache inconsistencies in an invalidation-based cache is very actionable and managable based on our experience.

[ Parent | on HN ]