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

The NoSQL Dogma

Whats the point?

MySQL is a proven technology, its engines are stable and well known, and scalable ( Yep modern forks for clouds are already rolling one example is drizzle); so I can’t find any point in shifting to a technology thats a new born, adds more calories to my code, and then brag about it just because its a buzz word! Untill there is no genuine reason to have a noSQL its just a trendy statement!

It is true that removing the SQL processing overhead will give MySQL a speed boost. But let’s not forget that:

  1. with a similar setup, a NoSQL solution like Redis might give you even more operations per second
  2. key-value only access might not be enough. Many NoSQL solutions are offering at least MapReduce support.

What I’m trying to say is that if you need a key-value store, even if MySQL engines are stable and well tested, you should still take a look at real key-value stores.

And if more than key-value access is needed, give MapReduce a try as translating SQL to MapReduce is not so complicated.

Original title and link: The NoSQL Dogma (NoSQL databases © myNoSQL)

via: http://maxpert.tumblr.com/post/3329352663/the-nosql-dogma