(1) Dynamo operates with high consistency at the cost of weaker availability. It is designed to be ‘‘Eventually Consistent’’
where consistency is maintained through ‘‘Object Versioning’’. As the system aims to provide an ‘‘always writable’’ state, the conflicts are resolved in the read operation using the versioning and application-specific resolution protocols. When dealing with the uncertainty of the correctness of an answer, the data are made unavailable until it is absolutely certain that it is correct. Dynamo points to self-repair mechanisms in the key-value store to implement eventual consistency in practice [18].