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



Victims of the SQL Hammer

The first thing you need to realize is that you’re a victim of the SQL hammer. If having a hammer means everything is a nail, then it’s the same for SQL. Imagine, for instance, that Google’s search engine (which is trying to deliver information that is personal and relevant to you) was built by a group of SQL engineers. First, they would have designed a global data schema for all the information on the planet. Then they would have used the extract, transform and load (ETL) process and data-cleansing tools to bring all the information on the planet into their global SQL database. Finally, they would write reports such as: “Places to camp in France,” or “Chinese restaurants in Hickory, N.C.” After 10 years and tens of millions of dollars, the team would probably have given up. Fortunately, Google didn’t take that approach.

As much as I support the NoSQL space, I’ve already seen victims of the NoSQL hammer in only 2 and a half years. Both the hammer and new shiny toy syndroms are as present. One could even say that you cannot have the one without the other.

Original title and link: Victims of the SQL Hammer (NoSQL database©myNoSQL)