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
Monday, 23 July 2012
‹ Back

Hadoop’s Shortcomings

About:
,
,
,

Andrew Brust for ZDNet:

Performing analytics on clickstream and log file data are canonical examples of Big Data in action; they represent a sweet spot for the technology. Hadoop is also a canonical example of Big Data in action and, more and more, Hadoop and Big Data are taken as synonymous. But from recent discussions with Web analytics stalwart Webtrends and log file analytics startup Loggly, I’ve come to learn that these core Big Data scenarios do not always mesh well with Big Data’s best known technology.

What are these shortcomings? The answer is already known by everyone that used or at least read something about Hadoop: Hadoop is not real-time. What a surprise!

Original title and link: Hadoop’s Shortcomings (NoSQL database©myNoSQL)

via: http://www.zdnet.com/webtrends-loggly-explain-hadoops-shortcomings-7000001429/