The “Big” Fallacy of Big Data

The “Big” Fallacy of Big Data

Unless you’ve been living under a rock for the past couple of years, you’ve been hearing about the world of Big Data nonstop. Big Data promises fortune and power to those that can wield the somewhat mystical and often nebulous power of “Big Data”. Unfortunately for the rest of us mere mortals Big Data is built on an out-right lie that is both pernicious and unfortunate. It’s hiding right there in plain sight in the name itself. The word, BIG.

The Fallacy of Big Data is that you have to have a lot of data for it to be relevant. The common catch phrase is: "More data = more insights". There is a nugget of truth to this in that, in some cases, a lot of data is needed in order to establish valid patterns and create real insight into the activity the data represents. More often than not however, this creates a significant challenge to those responsible for performing analytics which is sifting through a mountain of data to find the parts that actually matter. Recent studies have shown that fully 80% of data analysis is spent just tinkering with the data to get it into a usable format. So we see that more data creates a massive data curation issue, and leaves us with more work to do to even start experimenting, much less monetizing our data.

The reality of “Big Data” is that it was invented by those with no skin in the game. Analytics, open source, digital transformation, and Cloud are all of the technologies that enable comprehensive data analysis. With minimal infrastructure, commodity hardware, and free or nearly free software to store, analyze, and more importantly drive value from that data, the big infrastructure players are left out in the cold with nothing to offer. Enter “Big Data”, because if you are going to try and manage petabytes of data you need good storage, and 10’s of thousands of servers is awful to manage. So the Fallacy is born:

"In order to get real results from data, you cannot rely on just a little bit of it, or just the relevant data, you need every set of data imaginable. Therefore, (and here's where things get squidgy) you need to bring all that data in house (because the cloud is too expensive to store it) and you need a lot of manageable and flexible enterprise-grade gear to do it with (because free stuff is not enterprise ready)."

You can see how this is built around some nuggets of truth. I was asked recently, "how would you move a petabyte of data to Amazon cloud storage?" and I answered as truthfully as I could, "Very Slowly". Cloud does get expensive when used for a lot of infrastructure, but when used as a part of the overall solution it is an important tool. Also the thought of managing a massive Hadoop cluster of 1000 "exactly the same" servers sounds like the hell of IT in the pre-VM days, but it is also not really an accurate picture of the Hadoop landscape. The vast majority of analytics clusters top out around 50 servers and that's far more manageable (and less expensive) than huge enterprise gear. To be fair, there are organizations out there where a massive-scale, enterprise platformed approach will make sense, but the unfortunate side effect of this approach by legacy vendors is that they have made the solution itself the barrier to entry.

The problem is that now “Big Data” has made it into the vernacular and worse yet, has become synonymous with Data Analytics. Every company, organization, or even individual on earth can benefit from analyzing their relevant data for new insights. Take a very simple example; look at your budget to identify where you overspend (too many meals out for example). That is personal analytics, it does not require complex anything, and there are numerous ways to do it with free or nearly free tools. Now scale that up to the bank that wants to offer new digital, data-driven products to customers. They already have a lot of that data in house, and they already have a lot of analytical tools. Why would they need, per-se, to include every data set under the sun? They may want some more sets of data (social media to identify trends that might lead to investment opportunity), but they don’t HAVE to have it stored in house to use it - it is all offered free-to-use via serialized API's. In the unique case where if they did decide to store it all in house, we are not talking about 10’s of PB of data. More like adding a few 10’s to 100’s of TB for the data in question, because again - you don't download all of Twitter, just the stuff that is relevant to you. Also analytic data is largely transient data, meaning that it is used for the analysis and then discarded (especially true in the real-time world), so where is the need for massive infrastructure to support that initiative?

I have spoken a lot about “Big Data” and the Fallacy and trap of paying too much attention to the word BIG. Data is important to everyone and it can have value for anyone. In my most recent speaking sessions I have shown how you can do a simple social analysis for free in a matter of minutes. You don’t need a massive infrastructure to make that production ready either. It just takes some willingness to see through the noise to the actual value of what the “Big Data” message is trying to say. Analytics is important and valuable for everyone. You don’t have to be a Fortune 100 company to create value from the data you already have, and to bring in new data for analytics. Everyone can do it.

Interesting post, Chris. I agree that 'big data' is often used as a synonym for analytics, which causes confusion between IT operational people and the data science people.

Like
Reply

Great post, Chris! I myself like the idea of the "right data" versus big data. I could see "data hoarding" happening due to the belief that more data equals more insight (or conversely, that not looking at all of the data doesn't provide a complete picture, causing you to miss something important). I'd be interested in your opinion on how you know you have all of the data you need, and "when to say when" - or is data curation an ongoing evolution?

Like
Reply

getting the data to match the use case is problem. so it is not lots of data; rather useful data whatever that may be. when it comes to healthcare fraud, you can suspect provider fraud from 10 rows of data. For example, I saw new patient evaluation and management procedure codes such as 99201 to 99205 applied consistently on medicare patients. The procedure code should be 99211 to 99215. In other case, I saw internal organ burn on a rather uncomfortable level in car accident fraud claims. So there are cases where Big data is also small data; you catch millions of dollars very quickly because you know how to do more with less.

Like
Reply

As Carr - 'Nothing more reproducible than a byte', but nothing more expensive to obtain than a correct byte in the first place

To view or add a comment, sign in

More articles by Chris Harrold

Others also viewed

Explore content categories