Skip to main content

Additional dimensions of Big Data - discussion revived once more


We have earlier as well heard of Big Data dimensions beyond the conventional 3 popularized by IBM and the akin: Volume, Variety and Velocity. The discussion is now revived once more after Mark Beyer, Gartner Research VP, addressed the gathering at Oracle Open World 2012 and brought his 12 dimensional framework for Big Data to the fore.

(Based on what has been heard, during the same session George Lumpkin, Vice President, Product Management also talked in grand Oracle fashion about Oracle’s In-Database Hadoop claims while the purists whispered their genuine queries on real time processing.

However, besides the hype was the informative talk from Mark who was co-hosting the session with George.)

To understand better what Mark said, let’s dust off a Gartner report from 2011 which says that Big Data is only the beginning of extreme information management.

According to Gartner’s research team comprising of Mark Beyer, Anne Lapkin, Nicholas Gall, Donald Feinberg, Valentin T. Sribar,  Big Data has more often than not been defined under various terms which include Real-time data, Shared data (data shared across apps), Linked data (inter-related data from various sources) and High-fidelity data (containing context, detail, relationships and identities of important business info).

Extreme information management, according to them, pertains to dealing with issues across a dozen different dimensions in three categories: quantification, access and quality assurance.

Quantification:
Volume of data
Velocity of data streams, access demands and record creation
Variety of data formats
Complexity of individual data types (standards, domain rules, storage formats for each asset type)

Access enablement and control:
Classification (sensitive/non-sensitive, private/public classifications and so on)
Contracts (agreements on who will share information and how)
Pervasiveness (how long does data remain active)
Technology-enablement (specifications for tools and technology)

Qualification and assurance:
Fidelity (ability or inability to confidently adapt an asset for wider use)

Linked data (data in combination and the uses related to this context)

Validation of data (ensuring data is valid per use case)
Perishability (longevity, aging of data while retaining its state and character)


In a nutshell, the Extreme Information Management framework definitely poses a unique opportunity to assess the key challenges faced in the Big Data explosion. CIOs must recognize the signs of these challenges while tapping data for a competitive advantage.  From a pure analyst perspective, we know there is no single tool that fits the bill per this framework.  Today it requires a huge environment to be in place to meet these needs and challenges posed by the Big Data world. We just hope as the ecosystem matures up, we can start putting more tick marks on each enterprise’ EA against this dimension list. 

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…

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 …