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

Why a DiY Big Data Stack is a Better Option

Someone is hopefully kidding:

While settling on a standard big data stack is deeply important to the big data industry as a whole, I’m nonetheless questioning the operational and competitive consequences for companies who choose to buy into this standard without first considering the value of building their own proprietary solution. […] The other benefit to going our own way is a sustainable competitive advantage over time.

I’m not sure a storage solution actually represents competitive advantage, but I’m wondering if you shouldn’t focus first on getting your business up and profitable, before investing your engineering efforts in building yet another storage solution?

Original title and link for this post: Why a DiY Big Data Stack is a Better Option (published on the NoSQL blog: myNoSQL)

via: http://cloud.gigaom.com/2010/09/04/why-a-diy-big-data-stack-is-a-better-option/