Skip to main content

Hadoop is hot, Cloudera is 'sexy'

By Desk Editor

So, you heard it… Cloudera was the runner-up in ‘Sexiest Enterprise Startup’ category of The Crunchies. The awards were co-hosted by GigaOm, VentureBeat and TechCrunch and aimed to recognize the most compelling startups, internet and technology innovations of the year. The ‘Sexiest Enterprise Startup’ award category was added this year where Box bagged the winning honor while Cloudera was honored with runner-up.


This is not the first award that Cloudera got and has made a habit of being at the right place at right time. Let’s analyze 5 key strategic moves that Cloudera has been making to keep it continually attractive:

1) Partners:

- Cloudera has association with some of the best names in the enterprise IT vendor world. During its initial euphoria Apache Hadoop started off a threat wave to relational database but today Cloudera seems to have settled to a symbiotic co-existence with IBM and Oracle products. Similarly, other hardware and software giants including Dell, HP, CISCO and NetApp add to this prestigious list of associations.  From a wider ecosystem perspective, Cloudera has 119 partners on last count.

2) Brand Ambassadors:

- If you are looking for Hadoop evangelists and brand ambassadors, look no further. Starting with Doug Cutting to the whole list of stars that address key note events and dominate media, Cloudera today has created many more brand ambassadors than any other startup in a similar time frame. Olson, Amr, Hammerbacher, Lipcon, White ... this Hadoop ambassador list is ever expanding and always seems to be adding Cloudera stars.

3) Go East, Go West:

- USA, UK and then Japan. Hey wait; are we talking Cars or IT? In a strategic move, Cloudera is one of the few companies who have established a key presence in Japanese market. Japan is one of the heavy industrialized nations which utilize IT for automation with intensive batch jobs. Some of the big names like Toshiba, Fujitsu have done PoC on Hadoop and Cloudera seems to have noticed that potential early enough.

4) Social Media and Search Engine optimization:

- Highly optimized website for search engine combined with smart social media campaigns from the company and individual contributor accounts, Cloudera has played smartly on digital presence. Unlike MapR which has relied quite a bit on PPC, Cloudera today has built up its online backlink and referral network aggressively in the last 2 years.

5) Influencer:

- There is bright talent pool at Cloudera not just in engineering staff but also within the Board and Management. While the engineers continue to make forays out of Cloudera starting up their own new ventures, the executives register their presence in some key venture funding decisions. Overall, a big big influencer in entire startup sphere.

The above points focus on aspects beyond its technical leadership and innovations. Last year, they demonstrated technical brilliance with real time querying in Impala and this year we can expect the momentum to add up with Trevni. Meanwhile, keep following and stay tuned.

___________________________________
image courtesy: freedigitalphotos.net
Labels:

Comments

Post a Comment

Popular posts from this blog

In-memory data model with Apache Gora

By Sachin Ghai
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…
4 comments
Read more

Data deduplication tactics with HDFS and MapReduce

By Desk Editor
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…
Post a Comment
Read more

Amazon DynamoDB datastore for Gora

By Sachin Ghai
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…
1 comment
Read more