Skip to main content

Apache Hadoop ecosystem - March 2013

Apache Hadoop ecosystem continues to evolve at a rapid pace with newer projects that are being added as incubators while those currently under incubation are getting ready to graduate out. Let’s visit the current state of open source Apache Hadoop ecosystem.


(Slides may render differently on browsers - in certain cases font, links and curves may not appear as intended. Use contact option to receive original presentation)


About the categorization:
(1)   Core Layers – this category comprises the core components which are required in part or as a whole to optimally leverage Apache Hadoop
(2)  Atmospheric Layers – this category comprises the additional components which provide advanced capabilities and insights for the composite use cases.

The nomenclature adopted for categories (core/atmospheric) and layers does not constitute official lingo and are being introduced to demarcate the basic use case versus advanced use cases of Apache Hadoop. As Hadoop distribution matures out along with technology stacks built up by organizations, we expect components and probably even layers to move around from one category to other.

Other open source projects/components like Cloudera Impala, Kerberos, Protocol Buffer etc. are not included in this ecosystem diagram since they are not Apache Software Foundation (ASF) projects.



Comments and inputs are welcome.


You may also download the full size image.



If you would like to contribute your content to hadoopsphere.com, click here.


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 …