News for hackers. Stuff that matters.

A comment on S3 Strong Consistency. Parent comment

Re:S3 Strong Consistency by throw93 on Wednesday December 02, 2020 @01:42PM (#25279769)
>> Let's say that their consistency model is achieved via quorum, that is writes write to a quorum of nodes while reads read from a quorum of nodes (of their metadata database) then this guarantees read after write consistency.

If reads are reading only from a quorum of nodes how do you guarantee they have latest data? In theory, while a node is servicing a read request wouldn’t you need to query “all” other nodes to verify that the data in current node is latest? What if the quorum of nodes don’t have the latest data yet?

[ Parent | on HN ]
Re:S3 Strong Consistency by YZF on Wednesday December 02, 2020 @10:36PM (#25285060)
You write to a quorum of nodes and you read from a quorum of nodes. Latest is determined by a clock. Let's say you wrote to 2 out of 3 nodes, and read from 2 out of 3 nodes, one of those 2 you read from is going to have the latest data. This is how consistency works in Cassandra e.g.

There are other models, for example by using a consensus protocol.

[ Parent | on HN ]