Eventual consistency is a consistency model used in distributed computing that informally guarantees that, if no new updates are made to a given data item, eventually all accesses to that item will return the last updated value.

- Stackoverflow.com Wiki
2 articles, 0 books.

New people to Apache Cassandra are often concerned about the phrase "eventual consistency." It's one of those things that seems so foreign, especially if you're coming from a relational database. When I am with with my RDBMS I get wrapped in the sweet cocoon of ACID transactions!


Doesn’t the CAP theorem state that we have to choose consistency over availability, or availability over consistency? Over the years, Google has been arguing that you can have both strong consistency and high availability, and that you don’t have to settle for eventual consistency.