Can someone please create a page redirecting Basically Available, Soft state, Eventual consistency to this page? 188.8.131.52 (talk) 17:28, 19 April 2011 (UTC)
Does a single white paper from Amazon (which AFAIK introduced the term), and a single reference to an ACM article really qualify this as "database terminology"? As I understand it, the term did not exist even 3 years ago. --184.108.40.206 (talk) 11:04, 6 August 2011 (UTC)
Would be nice to have a reference to Amazon's whitepapers and to other data store products built around this paradigm (Amazon Dynamo, LinkedIN's Project Voldemort, Riak, etc... ) 220.127.116.11 (talk) 05:34, 28 March 2012 (UTC)
Similar or Related Concepts in Accounting
I've heard that eventual consistency is similar to certain traditional accounting practices, such as "closing the books" over various time intervals: daily, weekly, monthly, quarterly, annually, for purposes of establishing backdated points of truth on which later (accounting) consistency can be based. Can anyone reading this identify any articles or sources to verify this claim? (Inclusion in the article would be subject to the WP:NOR guidelines, of course). — Preceding unsigned comment added by JimD (talk • contribs) 05:11, 28 May 2014 (UTC)
- I don't think that's a useful analogy. If the data keeps changing then an "eventual consistency" system never actually reaches a consistent state and that's the normal mode of operation. -- intgr [talk] 07:19, 28 May 2014 (UTC)
ACID vs BASE ???
I cannot imagine how ACID and BASE can possibly be considered mutually exclusive. ACID is about write operations on an individual server, BASE is about replication between at least 2 servers. You can achieve eventual consistency on a replication environment with a fully ACID-compliant DBMS. This is the most common situation. — Preceding unsigned comment added by 18.104.22.168 (talk) 23:51, 6 July 2014 (UTC)