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

When to Use and Not to Use Hadoop: Hadoop vs ELSA

Forget for a minute you didn’t hear about ELSA and go through the post as it’s a good read about Hadoop’s pros and cons even if its main intent is to make you think “my ELSA is better than your Hadoop”:

The easiest alternative to using Hadoop for Big Data is to use multiple traditional databases and architect your read and write patterns such that the data in one database does not rely on the data in another.  Once that is established, it is much easier than you’d think to write basic aggregation routines in languages you’re already invested in and familiar with.  This means you need to think very critically about your app architecture before you throw more hardware at it.

This is the theory. For the practical part use something that works.

Original title and link: When to Use and Not to Use Hadoop: Hadoop vs ELSA (NoSQL database©myNoSQL)

via: http://ossectools.blogspot.com/2012/03/why-elsa-doesnt-use-hadoop-for-big-data.html