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

In-memory data model with Apache Gora

Open source in-memory data model and persistence for big data framework Apache Gora™ version 0.3, was released in May 2013. The 0.3 release offers significant improvements and changes to a number of modules including a number of bug fixes. However, what may be of significant interest to the DynamoDB community will be the addition of a gora-dynamodb datastore for mapping and persisting objects to Amazon's DynamoDB. Additionally the release includes various improvements to the gora-core and gora-cassandra modules as well as a new Web Services API implementation which enables users to extend Gora to any cloud storage platform of their choice. This 2-part post provides commentary on all of the above and a whole lot more, expanding to cover where Gora fits in within the NoSQL and Big Data space, the development challenges and features which have been baked into Gora 0.3 and finally what we have on the road map for the 0.4 development drive.
Introducing Apache Gora Although there are var…

Amazon DynamoDB datastore for Gora

What was initially suggested during causal conversation at ApacheCon2011 in November 2011 as a “neat idea”, would soon become prime ground for Gora's first taste of participation within Google's Summer of Code program. Initially, the project, titled Amazon DynamoDB datastore for Gora, merely aimed to extend the Gora framework to Amazon DynamoDB. However, it seem became obvious that the issue would include much more than that simple vision.

The Gora 0.3 Toolbox We briefly digress to discuss some other noticeable additions to Gora in 0.3, namely: Modification of the Query interface: The Query interface was amended from Query<K, T> to Query<K, T extends Persistent> to be more precise and explicit for developers. Consequently all implementors and users of the Query interface can only pass object's of Persistent type. Logging improvements for data store mappings: A key aspect of using Gora well is the establishment and accurate definitio…

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…