There’s a good chance that you’re not using Hadoop right now. Hopefully you’ve moved past your fear of the unknown and you’re ready to embrace something new. If not, you should go read some Marmaduke and come back when you’re ready.
We’re a Windows Shop
That excuse doesn’t fly anymore. Earlier this year, Hortonworks released version 1.1 of their Hortonworks Development Platform for Windows. Microsoft have also released HDInsight (Hadoop as a service) in Azure as well as a developer preview of a local version of HDInsight.
If Windows was the reason you weren’t using Hadoop, you need to come up with a new reason.
I Don’t Know Java
Fair enough – you don’t know Java. Hadoop is written in Java and MapReduce jobs, the core of Hadoop, are typically written in Java as well. I don’t know C++, but I can still use SQL Server. What’s up with that?
There are a number of high level abstractions on top of Hadoop that make it easier to work with big data – Hive and Pig provide data manipulation languages. When you need them, MapReduce jobs can be written in many languages and frameworks. Besides, Java looks enough like C# that you should be able to pick up the broader points in a weekend.
Heck, I’ve even put together an introduction to Hadoop to help get you started.
We Don’t Have Petabytes of Data
Neither did Lands of America, but they were able to take advantage of Hadoop to solve their data processing problems and get additional insight into their business. Although the data volume was under 1 terabyte, the processing problems were very real, but they were solved by scaling out the processing across a Hadoop cluster.
What’s the Real Reason?
So what’s the real reason? Sound off in the comments and let me know why you’re not using Hadoop.