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



The document is the single source of truth

Paul Hammant:

When it comes to data storage the obvious conclusion is that the backend should save something pretty close to the document that the client presents, mutates, and sends back to the server for posterity. […] Use a document store instead. When would you use a normalized DB design today? The answer to that is: only when you have other processes reading and writing to your database.

There are a few scenarios where data is always accessed in the same format and that’s where document stores excel. For the rest of the scenarios, there’ll always be a trade-off between optimizing for the most frequent access patterns vs the additional processing required to provide different perspectives on the data.

Original title and link: The document is the single source of truth (NoSQL database©myNoSQL)