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 Has Promise but Also Problems… Show Me the Cheaper or Simpler Alternatives

Jessica E. Vascellaro for WSJ:

But some early adopters of Hadoop now say using the technology is challenging and rolling it out will take time.


Mr. Boroditsky says Hadoop is “immature” and comes with additional costs of hiring in-house expertise and consultants. “There is a very substantial cost to free software,” he says, declining to comment on dollar figures.

I’m starting to believe that the “Hadoop has problems and is complex” chorus is a vendor reaction very similar to the reaction they had to open source in general. Thus, before joining the group complaining about the complexity, costs, and lack of know-how, ask yourself the following questions:

  1. how many other tools can lead you to the same solution?

    Here are a couple of examples of what people choosing Hadoop had to say:

    • Infolinks using HBase and Hadoop:

      We started exploring the NoSQL solutions more than a year ago. We did some research on the available solutions and chose Hadoop/HBase for few reasons: 1. Java based 2. Open source 3. Hadoop - quite mature compared to other Java based solutions. Hadoop is also used by many web companies. 4. HBase - using Hadoop (so you get for free Hadoop stability, APIs etc.), like BigTable

      We tested this solution for 6 months (as a small cluster) and were very happy with it.

    • Zions Bancorporation after reaching the limits of Data Warehouse technologies:

      The quest for a solution began in 2009 with an investigation of Zion’s existing Microsoft and Oracle technologies, as well as other technologies within the firm and new solutions on the market, Wood relates. After developing a list of six potential vendors, he says, he and his team quickly focused on two Hadoop-based solutions. The team, Wood explains, recognized the potential in Hadoop for “making security decisions proactively rather than reactively, based on mining business intelligence and combining it with event data from security devices.”

  2. based on the list of tools helping you solve the same problem:

    1. how many are cheaper for your scenario?
    2. for how many of them you’ll find more resources?
    3. how many are operationally simpler?
  3. how many of these tools evolve as fast as Hadoop and its ecosystem?

  4. how many of them allow you to go beyond the initial scenario and start addressing other questions?

    Here is what people say about what happens after adopting Hadoop.

It would be great if Hadoop administration would get simpler and operational costs would go down and if know-how would be easier to find. Rest assured that all these will happen. And if for the time being these are problems you cannot overcome, tell me about the alternatives.

Original title and link: Hadoop Has Promise but Also Problems… Show Me the Cheaper or Simpler Alternatives (NoSQL database©myNoSQL)