re: Scalable architecture without magic (and how to build it if you’re not Google) VIEW POST

VIEW PARENT COMMENT VIEW FULL DISCUSSION
 

Thank you for your reply! Your answer prompted me to do some reading. If I understand correctly, it seems that this kind of approach relies on the idea of "eventual consistency." However, if that is the case, it does seem that different nodes can potentially return different versions of the same information. That is, a node can potentially answer a query with data that is not up-to-date (over some finite interval of time) even when there are other nodes that do have the up-to-date information. This is something I am interested in, but do not have experience with, so do let me know if I've misunderstood, or if Riak works differently from "basic" eventual consistency...

Yes, you’re right. At distributed system, you can go for ACID, but it will be slower. However, Riak seems to use eventual consistency and vector clock:
docs.basho.com/riak/kv/2.0.1/learn...

In CRDTs, the Cap theorem is always taking place.

code of conduct - report abuse