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



Hadoop or Data as a Platform or Operating System... Which One Is It?

IDG Network Brian Proffitt revealing the (Hadoop or data) as a (platform or operating system):

Now, I’m no Super-Genius like Wile E. Coyote, but it occurs to me that if you have an application framework that developers could point to in oder to Get Stuff Done, then that seems suspiciously like a platform.

An observation I ran past Murthy when I bumped into him in the lobby at Strata. Given that Hadoop’s MapReduce framework was about to become quite a bit more robust, isn’t this just a set up for taking Hadoop on the path to becoming an operating system?

  1. Hadoop, not data.
  2. Platform, not operating system

It’s good to use all possible keywords in a post, but stick with those that actually make sense. Plus it’s usually helpful to do some reading before writing: Hadoop 0.23 already ships with MapReduce and a Distributed Shell as applications and there is ongoing work to also have a Message Passing Interface (MPI) applications.

Original title and link: Hadoop or Data as a Platform or Operating System… Which One Is It? (NoSQL database©myNoSQL)