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
Wednesday, 25 July 2012
‹ Back

Attacking Hadoop’s HDFS: 8 Ways to Replace HDFS

About:
,
,
,
,

Derick Harris for GigaOm:

Ironically, one of Hadoop’s biggest shortcomings now is also one of its biggest strengths going forward —the Hadoop Distributed File System.

But if the growing number of options for replacing HDFS signifies anything, it’s that HDFS isn’t quite where it needs to be.

No alternatives => vendor lock-in => bad

Multiple options => proof of weaknesses => bad

Confused? I am a bit.

Original title and link: Attacking Hadoop’s HDFS: 8 Ways to Replace HDFS (NoSQL database©myNoSQL)

via: http://gigaom.com/cloud/because-hadoop-isnt-perfect-8-ways-to-replace-hdfs/