Skip to main content

Making sense of Hype Cycle for Big Data



A few days back Gartner published Hype Cycle for Big Data,2012  and Hype Cycle for Cloud Computing,2012. We reviewed them and compared it with 2011 report and here are a few key new take-away from the 2012 Gartner reports.

The good news which had been expected by research followers is that Big Data has moved from ‘On the Rise’ to ‘At the Peak’.

However, the report goes on to add that Big Data will probably soon move into the Trough of Disillusionment in 2012 where it will mature in terms of offerings, solutions and technology maturity.  This was stated in its Hype Cycle for Cloud Computing, 2011 report also but seems Gartner is now more upbeat about technology players because it goes on to add “However, big data should spend very little time in the trough”.

The Hype Cycle for Cloud Computing, 2012 report also states that there will be attempts to combine MapReduce with Graph as well as natural-language processing and text analytics. Refer one of our articles on Facebook’s one such attempt among its many successful use cases.
The slight worrisome statement from the report is that “big data assets, such as images, video, sound and even three-dimensional object modeling, will also drive big data into the trough”. We know a lot of research is already happening on this and have in this site tried to cover one such architectural solution for Hadoop usage in video, sound search and modeling.

As in many other technology product life cycles, Gartner predicts that specialized technologies could become mainstream while newer technologies will emerge as the next major big data issue surfaces up.

In the Hype Cycle for Big Data, 2012, Gartner attributes one of the major reasons for increased focus on Big Data to “increased availability of scalable, elastic resources in the cloud have allowed organizations to begin big data projects without investing in infrastructure.”

It further details out 3 categories:
Entries that describe enabling technologies for big data
-          among the others, the one to note is column-store DBMS.
o        Refer our post on one such solution which uses column-store DBMS for higher performance

Entries that describe typical use cases for big data
-          among the other, the one catching attention is telematics

Entries that describe new information types, sources and roles
-          on expected lines, we know Data Scientist should feature here


For complete text, you may refer the 2012 reports at the links given above.  



Going a step further, we have applied Map Reduce on Hype Cycle for Big Data, 2012 report. We took all statements where Sample Vendors were suggested by Gartner in the technologies shown in Hype Cycle image at top. Our algorithm returned a count on how many times a vendor has been suggested in the report. The image below shows a graph generated by the data from MapReduce algorithm to arrive at a vendor mention count. (click on image to view full image).



: View full image on Pinterest




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…