This link has been bookmarked by 65 people . It was first bookmarked on 21 Dec 2007, by Steven Yamanaka.
-
24 May 17
-
Both require the client developer to be aware of what the system is offering. If the system emphasizes consistency, the developer has to deal with the fact that system may not be available to take for example a write. If this write fails because of system unavailability the developer will have to deal with what to do with the data to be written. If the system emphasizes availability, it may always accept the write but under certain conditions a read will not reflect the result of a recently completed write. The developer then has to make a decision about whether the client requires access to the absolute latest update all the time. There is a range of applications that can handle slightly stale data and they are served well under this model
-
- Strong consistency. After the update completes any subsequent access (by A, B or C) will return the updated value.
- Weak consistency. The system does not guarantee that subsequent accesses will return the updated value. A number of conditions need to be met before the value will be returned. Often this condition is the passing of time. The period between the update and the moment when it is guaranteed that any observer will always see the updated value is dubbed the inconsistency window.
- Eventual consistency. The storage system guarantees that if no new updates are made to the object eventually (after the inconsistency window closes) all accesses will return the last updated value. The most popular system that implements eventual consistency is DNS, the domain name system. Updates to a name are distributed according to a configured pattern and in combination with time controlled caches, eventually of client will see the update
-
-
27 Dec 14
-
23 Jan 14
William GunnXie: Inconsistency in Twitter #altmetrics is side effect of "eventual consistency" systems used by large webservices: http://t.co/nnpyOg8bz1
-
20 Nov 12
-
The period between the update and the moment when it is guaranteed that any observer will always see the updated value is dubbed the inconsistency window.
-
-
19 Sep 12
-
14 Jun 11
-
20 Jan 11
-
22 Dec 10
-
21 Nov 10
-
29 Oct 10
-
28 Apr 10
-
22 Mar 10
-
07 Dec 09
-
01 May 09
-
16 Apr 09
-
20 Nov 08
Hugo ZondaInteresting readings from Werner Vogels.
-
Niko SchmuckInteresting readings from Werner Vogels.
-
25 Oct 08
-
21 Sep 08
-
25 Aug 08
-
22 Aug 08
DJHell .Recently there has been a lot of discussion about the concept of eventual consistency in the context of data replication. In this positing I would like to try to collect some of the principles and abstractions related to large scale data replication and t
Cloud Computing eventual consistency ungelesen importiert Cloud Computing
-
24 Jul 08
-
23 Jun 08
Tim Lossen"Recently there has been a lot of discussion about the concept of eventual consistency in the context of data replication. In this positing I would like to try to collect some of the principles and abstractions related to large scale data replication ..."
-
12 Jun 08
Andrew GilmartinI would like to try to collect some of the principles and abstractions related to large scale data replication and the trade-offs between high-availability and data consistency.
-
06 May 08
-
22 Apr 08
-
06 Feb 08
-
31 Jan 08
-
18 Jan 08
-
14 Jan 08
-
11 Jan 08
-
07 Jan 08
-
03 Jan 08
-
31 Dec 07
-
23 Dec 07
-
21 Dec 07
-
20 Dec 07
tvaananenWerner Vogels talks about distributed systems and eventual consistency vs. the ACID properties.
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.