Croll espoused the virtues of eventual consistency.
Croll认可了最终一致性的优点。
In this context, the concept of eventual consistency started to win the ground.
在此前提下,最终一致性(eventual consistency)的概念开始赢得关注。
The second limitation is the eventual consistency approach that Amazon takes with the queue.
第二个限制是Amazon应用于队列的最终一致性方法。
Instead of focusing on all three, Amazon chose to focus on high availability and scalability and to provide eventual consistency.
Amazon不是关注所有3个特征,而是主要关注高可用性和可伸缩性,然后再以此为基础提供最终的一致性。
Weak/eventual consistency happens when not all data replicas participate in the update operation and/or contacted as part of read operation.
只有部分数据副本参与更新操作,且/或作为读操作的一部分与其它副本进行联系时,就会出现弱/最终一致性。
There are a number of practical improvements to the eventual consistency model, such as session-level consistency and monotonic reads, which provide better tools for the developer.
有很多改善最终一致性模型的实用方法,比如会话级别的一致性和单调读一致性,它们都为开发人员提供了更好的工具。
SQS follows the model of "eventual consistency," meaning you can send a message to the queue, but a consumer of that queue may not see the message for some significant period of time.
SQS 采用 “最终一致性(eventual consistency)”模型,这意味着您可以向队列发送消息,但是队列的消费者不一定能够在特定的时间段内看到它。
Eventual Consistency - data is not immediately propagated across all nodes... the latency is usually around a second, but for high data sets or loads, you may experience more latency.
一致性延迟——数据不是马上传播到所有节点的……延迟一般在1秒左右,但如果数据量或者负载很大,你可能遇到更多延迟。
Eventual Consistency - data is not immediately propagated across all nodes... the latency is usually around a second, but for high data sets or loads, you may experience more latency.
一致性延迟——数据不是马上传播到所有节点的……延迟一般在1秒左右,但如果数据量或者负载很大,你可能遇到更多延迟。
应用推荐