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

The NoSQL conundrum: Lagged veracity and the double-edged promise of eventual consistency

Very interesting article by James Kobelius expanding the V’s model to NoSQL databases. The article is focusing mostly on a 4th V, veracity which translates to how databases deal with consistency.

All of which raises a huge issue for NoSQL databases: in their current incarnations, with this veracity limitation, can they evolve into OLTP and/or EDW roles? After all, the very concept of a “system of record” or “single version of the truth” depends on having a database that supports low-lagged high veracity.

The only thing missing from the article is a look at what happens with the first 3 V’s when RDBMS choose the last V.

Actually we might already know the answer. There’s almost no Variety. And to get Volume and Velocity you have to pay a Very-high price. Still 4 V’s.

Original title and link: The NoSQL conundrum: Lagged veracity and the double-edged promise of eventual consistency (NoSQL database©myNoSQL)

via: http://www.ibmbigdatahub.com/blog/nosql-conundrum-lagged-veracity-and-double-edged-promise-eventual-consistency