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

Hadoop and Appliances

Curt Monash:

But it turns out technology isn’t the only reason to like appliances. Sometimes, internal politics hold sway. Suppose central IT is in control of normal computing installations, but departments can buy and control their own appliances? Then those departments might avoid bureaucracy, internal chargeback costs, and all the other things they hate about IT … but only if they go the appliance route. It turns out that this can be a very real consideration.

For startups budget is limited. For enterprises time is limited and bureaucracy is unlimited.

Curt is ending the article by saying he doesn’t see a future for Hadoop appliances. But judging by how many companies are trying to make a profit from Hadoop, I think we will actually see quite a few. I’ll throw out a couple of names even: IBM, NetApp, EMC — isn’t Greenplum HD a Greenplum + Hadoop appliance?

How these companies will name their appliances is another story, but most probably there will be a BigData in there and public announcements will talk about Hadoop commitments.

Original title and link: Hadoop and Appliances (NoSQL databases © myNoSQL)

via: http://feedproxy.google.com/~r/MonashInformationServices/~3/grwG0Ssbg3o/