ALL COVERED TOPICS

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

NAVIGATE MAIN CATEGORIES

Close

NoSQL? No Thanks

Steve Jones in “NoSQL? No Thanks“:

There continues to be a disproportionate amount of hype around ‘NoSQL’ data stores. By disproportionate I mean ‘completely and utterly out of scale with the actual problems of the vast majority of companies’.

Can you imagine how many such posts I’ve read since starting this blog? Sometimes I think that running a “Bashing NoSQL” blog could be a good business and help me fund this one too.

While there’s usually some truth behind every complaint about NoSQL, generalizations and are leading to less useful conclusions. For Steve Jones’s post, I’ll leave aside the clear example of an unnecessary generalization, that largely voids the points of the post, and try to focus on the rest.

The author suggests that the actual problems faced by “the vast majority of companies” are related to data interactions for traditional reporting, complex analytics, and embedding in applications. The hypothesis being that NoSQL databases and the Hadoop toolkit are making worse.

Put this way, it sounds right, isn’t it?

Before cars were invented, we had horses and carriages and dirt roads or no roads. Once the car was invented, people couldn’t ride their horses anymore, they couldn’t initially carry as much marchendise they did with carriages and on top of all these they had to redo the whole infrastructure. Cars made everything worse.

Both these arguments are missing the root cause. The whole rationale behind NoSQL databases and Hadoop is that the existing solutions were prohibitevely expensive for the the current requirements or they couldn’t handle the volume, velocity, variety, and variability of the data in this age.

There is no data interactions with no data. Little data means less useful reports and inaccurate or expensive data analysis.

Saying “no thanks to NoSQL and Hadoop” is implicitely saying no to the future of your business.

Last, but not least:

business users couldn’t care less what developers use as long as they deliver.

What’s the industry where technology doesn’t make the difference? If there’s one, how long it will last?

Original title and link: NoSQL? No Thanks (NoSQL database©myNoSQL)