Skip to main content

Hits and Miss among Hadoop use cases in 2012

2012 has been the year when Apache Hadoop hype reached its maximum peak till date. Along with the hype, came a lot of success stories around the adopted use cases. Let’s take a look at some of the Hits and Miss of Hadoop use cases.





Hits

1)      Seismic image processing

Chevron continued to demonstrate the huge technology initiatives if has taken with the help of Apache Hadoop. One of the major initiatives which gathered lime light (in 2012, though started earlier) was the processing of seismic data to detect presence of oil reservoirs.
source:: IBM Almaden

Under the sea subsurface information is collected by aggregating a large number of estimates from seismic waves. The process of creation of higher quality subsurface images has leveraged Apache Hadoop as a cheap and reliable technology option.


2)      Travel analytics:

Travel portals leveraged ApacheHadoop as one of the big consumers of this technology. With major projects undertaken in analytics and machine learning for online travel, the IT brains behind the portals leveraged the data crunching capabilities to the hilt.

Selective stories in online media combined with aggressive Hadoop skills hiring buzz continued to emphasize that Apache Hadoop is a definite hit with online travel.


Miss:


1)      Tsunami and Earthquake forecasting:

One of the grey areas where we would have liked Apache Hadoop to make a bigger impact was Tsunami and earthquake forecasting. We all realize the huge data sets that this problem relies on and how Apache Hadoop could be one of the prime candidates for processing. However, unfortunately, we failed to hear on any significant Apache Hadoop presence except for random interest sessions.

2)      Olympics problem:

The Olympics games at London was the biggest event in terms of Big Data generation through the year 2012. One of the big anxieties that was generated with Olympics was telecom network congestion. 80000 tweets per minute when Usain Bolt raced to glory and 118 million messages on San Weibo for opening ceremony – the data and statistics were just astounding.
But we failed to see an approach where Apache Hadoop could have been leveraged to predict network traffic or make provisioning arrangements during traffic peaks.

However, let’s not lose hope over here. Through the next few months, we will try to bring exclusive architecture approach for Tsunami forecasting and Olympics/Real life event mobile network provisioning. 

As we enter 2013, we see hope for many success stories and it will only be appropriate if hadoopsphere.com can contribute its little bit by demonstrating the power of IT for real life problems. So, stay tuned in 2013; keep mapping the real life problems while we all try to reduce their impacts.

Comments

Popular posts from this blog

Low latency SQL querying on HBase

HBase has emerged as one of the most popular NoSQL database offering distributed, versioned, non-relational tables hosted on commodity hardware. However, with a large set of users coming from a relational SQL world, it made sense to bring the SQL back in this NoSQL. With Apache Phoenix, database professionals get a convenient way to query HBase through SQL in a fast and efficient manner. Continuing our discussion with James Taylor, the founder of Apache Phoenix, we focus on the functional aspects of Phoenix in this second part of interaction.
Although Apache Phoenix started off with distinct low latency advantage, have the other options like Hive/Impala (integrated with HBase) caught up in terms of performance?
No, these other tools such as Hive and Impala have not invested in improving performance against HBase data, so if anything, Phoenix's advantage has only gotten bigger as our performance improves.  See this link for comparison of Apache Phoenix with Apache Hive and Cloudera Im…

Data deduplication tactics with HDFS and MapReduce

As the amount of data continues to grow exponentially, there has been increased focus on stored data reduction methods. Data compression, single instance store and data deduplication are among the common techniques employed for stored data reduction.
Deduplication often refers to elimination of redundant subfiles (also known as chunks, blocks, or extents). Unlike compression, data is not changed and eliminates storage capacity for identical data. Data deduplication offers significant advantage in terms of reduction in storage, network bandwidth and promises increased scalability.
From a simplistic use case perspective, we can see application in removing duplicates in Call Detail Record (CDR) for a Telecom carrier. Similarly, we may apply the technique to optimize on network traffic carrying the same data packets.
Some of the common methods for data deduplication in storage architecture include hashing, binary comparison and delta differencing. In this post, we focus on how MapReduce and…

Pricing models for Hadoop products

A look at the various pricing models adopted by the vendors in the Hadoop ecosystem. While the pricing models are evolving in this rapid and dynamic market, listed below are some of the major variations utilized by companies in the sphere.
1) Per Node:Among the most common model, the node based pricing mechanism utilizes customized rules for determining pricing per node. This may be as straight forward as pricing per name node and data node or could have complex variants of pricing based on number of core processors utilized by the nodes in the cluster or per user license in case of applications.
2) Per TB:The data based pricing mechanism charges customer for license cost per TB of data. This model usually accounts non replicated data for computation of cost.
3) Subscription Support cost only:In this model, the vendor prefers to give away software for free but charges the customer for subscription support on a specified number of nodes. The support timings and level of support further …