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



MongoDB and File System Durability Explained

I just found this post from Ivan Voras which is covering exactly what I’ve written a while back about MongoDB durability being a tradeoff. As a plus, Ivan’s post also includes a quick summary of various file system durability methods:

  • fully synchronous writes
  • partially synchronous writes
  • logging
  • journaling
  • soft updates

I only hope that based on these two posts, all MongoDB users will become aware of the MongoDB durability behavior (or differently put durability tradeoff).