News for hackers. Stuff that matters.
Re:Cache made consistent: Meta’s cache invalidation solution by uvdn7 on Wednesday June 08, 2022 @05:34PM (#31674597)
It's a good observation that out-of-orderness and asynchrony contribute a lot to the challenge.

> the inconsistency between your cache nodes is a consequence of the underlying design of your system

I disagree with this. First of all, imposing order and synchrony is expensive, slow and unreliable. Even if we do that, cache fill and invalidation will never be externally coordinated; and will collide on the cache host.

Re:Cache made consistent: Meta’s cache invalidation solution by wildmanx on Wednesday June 08, 2022 @06:21PM (#31675141)
> > the inconsistency between your cache nodes is a consequence of the underlying design of your system

> I disagree with this. First of all, imposing order and synchrony is expensive, slow and unreliable. Even if we do that, cache fill and invalidation will never be externally coordinated; and will collide on the cache host.

This is a weird reply. GP writes "A implied B" and you disagree by arguing that you had to do A. Sure. But it's still what implied B. Quite a fundamental logic flaw, no?

Re:Cache made consistent: Meta’s cache invalidation solution by uvdn7 on Wednesday June 08, 2022 @06:25PM (#31675190)
I don't see that. Yes I did say I had to do A. Then I said that it doesn't imply B. Because even if the underlying system is strongly ordered, we can't order external events. Did I miss something?
Re:Cache made consistent: Meta’s cache invalidation solution by wildmanx on Wednesday June 08, 2022 @06:33PM (#31675281)
A == "Design of your system"

B == "Inconsistency between your caches"

GP: A -> B

You: "Imposing order and synchrony is [bad things]" == "If you don't do A then [bad things]", i.e., (not A) -> [bad things]

Also you: "Even if we did, then [other issues]" == "Even if you don't do A then [other issues]", i.e., (not A) -> ..what? B?

You are certainly not arguing against the A -> B implication.

Re:Cache made consistent: Meta’s cache invalidation solution by uvdn7 on Wednesday June 08, 2022 @06:52PM (#31675458)
I really appreciate your comment. I am learning as we speak.

I was essentially saying !A !-> !B - even if we have a strongly ordered system, there will still be inconsistencies/races/problems.

And I can see why it's a bad/weird argument. Thank you for pointing it out. Really appreciate it!

EDIT: I would have rephrased it this way

- A -> B is right - But !A -> B also holds. Hence what we talked about here is relevant/useful regardless. And it's not about A.

Would that be better?