Re:There's Just No Getting Around It: You're Building a Dist...
by zip1234 on Thursday April 27, 2017 @02:04PM
(#14213518)
Seems like when cache needs to get involved, things can get complicated very quickly.
Re:There's Just No Getting Around It: You're Building a Dist...
by dmoy on Thursday April 27, 2017 @02:41PM
(#14213764)
One of the two hard problems...
Re:There's Just No Getting Around It: You're Building a Dist...
by hamandcheese on Friday April 28, 2017 @12:07AM
(#14216809)
I don't really see how your example applies to the point the root comment made. S3 surely _is_ a distributed system, but he is specifically talking about data residing on _one_ machine (notwithstanding the bits about read only followers).
But just because your storage layer is abstracted behind an API doesn't mean eventual consistency isn't your concern.
Take S3 for example.
LIST calls lag deletes but exists() doesn't, so exists() could return 404 for a document that's still included in the result of LIST. Plus, all exists() calls go through a caching load-balancer, so you could receive different answers in two subsequent exists() calls.
That's just a small subset. There's a good comment here[1] on S3's consistency semantics.
Point is, 12FA makes things easier but any time you have more than one computer involved (i.e, always), consistency becomes complicated.
[1] https://issues.apache.org/jira/browse/FLINK-5706