ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

Concurrent updates, distributed systems and clocks, vector clocks, last-write-win, and CRDT

Great post by John Daily from Basho about concurrent updates in the world of distributed systems and the implications of using clocks, vector clocks, last-write-wins, distributed data types (Commutative Replicated Data Type):

The problem is simple: there is no reliable definition of “last write”; because system clocks across multiple servers are going to drift.

Original title and link: Concurrent updates, distributed systems and clocks, vector clocks, last-write-win, and CRDT (NoSQL database©myNoSQL)

via: http://basho.com/clocks-are-bad-or-welcome-to-distributed-systems/