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



Why NoSQL does not Impress Me

Carl McDade:

I am not particularly impressed with CouchDB, MongoDB…Tokyo cabinet or any of the derivatives. Why not? Because it’s nothing new to the web or me as a developer. I was already using text/flat file databases back in 2003. […] To me it would have been very impressive if SQL was available as an option to map/reduce.


I have noticed that many that are hot on “NoSQL” are those that do not have any training or interest in learning about database architecture, design or optimization. To them things like CouchDB are away of escaping the need to learn these things. But what many don’t realize is that the replacement for SQL, Map/Reduce, is a more difficult and less intuitive way of querying the data source.


Most that ask me about NoSQL have never tried to distribute anything more than 10 gigs of data across a couple of database servers and a maybe two web servers. In other words they are sightseers looking for the latest craze but have no interest in learning anything about the internals or the proper uses of the “new/old” technology.

Some are good points, some are really bad.

Original title and link for this post: Why NoSQL does not Impress Me (published on the NoSQL blog: myNoSQL)