News for hackers. Stuff that matters.
Re:Cache made consistent: Meta’s cache invalidation solution by uvdn7 on Wednesday June 08, 2022 @07:54PM (#31676004)
> The "when" problem is dependent on your application architecture, not on your cache backend nor the number of keys in it.

I would argue the "when" problem is dependent on data models. And it's possible that we are referring to the same thing with different names.

> If, overall, you have an extremely simplistic application architecture

I mean FB is not a simple app. A complicated app can be built on a relatively simple data model as well (that's essentially how TAO works). But we do have memcache as well; and in some cases it can be complicated/hard. I can see that, and I won't argue against it.

> Yes, #2, can't be avoided. But, while it is interesting, and - in some cases, given a specific caching stack - it may be relatively hard, it's not a general problem.

I respectfully disagree. I explained in the blog post about why #2 is a generally hard problem. The analogy I like to use is Paxos. The protocol fits on a single slide. It's easier to feel like you have Paxos work; but it's very hard to have Paxos actually work.

Re:Cache made consistent: Meta’s cache invalidation solution by lucideer on Thursday June 09, 2022 @09:46AM (#31681066)
Paxos is an implementation (of protocols).

I think you fundamentally misunderstand what the word "general" means here.

Re:Cache made consistent: Meta’s cache invalidation solution by uvdn7 on Thursday June 09, 2022 @10:26AM (#31681571)
> Paxos is an implementation (of protocols).

I have nothing more to add, if that's your standpoint. But I am glad that we "debugged" to close to the "root" of our assumptions/context.