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



noSQL is what you need 99% of the cases

Let me put a disclaimer before I carry on. There might be situations where noSQL’s solution are absolutely illogical to use. But I firmly believe that if you are using a database for storing Ruby’s or PHP’s object into a database to eventually retrieve them later, you fit in my 99% case scenario.

Even if this is a blog about NoSQL databases and polyglot persistence, I cannot fully agree with that. Following the logic above one would use object databases in 99% of the cases. And reality shows things are different.

What I could agree with is that document databases provide a good balance between:

  • a flexible and close to the object-oriented world model
  • a decent querying model
  • better separation between data and behavior

But that’s far from saying document databases fit 99% of the scenarios.

Original title and link: noSQL is what you need 99% of the cases (NoSQL databases © myNoSQL)