> EDIT: Reading through "A real bug we found and fixed this year" and I'm still a bit confused. yeah that specific bug is convoluted. > It seems like a very c

> EDIT: Reading through "A real bug we found and fixed this year" and I'm still a bit confused. yeah that specific bug is convoluted. > It seems like a very contrived bug directed directly to how you deal with versioning (e.g. you allow the latest version to be present with stale metadata, or something?). This is mostly for performance reason that I won't go into details too much here. Version is mostly an internal concept that clients don't care about. So it's OK-ish. > My main concern with cache invalidation is what to invalidate at what time. Can you elaborate? Our experience on cache invalidation is that you invalidate on mutation, and in terms of "what to invalidate" it depends on the computation, which you might have to give me a little more details.