DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
11 Monitoring and Observability Tools for 2023
Learn more
  1. DZone
  2. Data Engineering
  3. Big Data
  4. Why Isn’t Big Data Called Small Data?

Why Isn’t Big Data Called Small Data?

If there were a more accessible adjective to discuss ''big'' data, then maybe, just maybe, more people would be comfortable exploring it.

Matthew Reaney user avatar by
Matthew Reaney
·
Apr. 28, 17 · Opinion
Like (3)
Save
Tweet
Share
9.05K Views

Join the DZone community and get the full member experience.

Join For Free

Sometimes, I think that Big Data has a branding problem.

You see, for data scientists to gain trust and buy-in from their colleagues, they have to explain how their analysis can add value. They take a “data ocean” of information and distil it into highly specific and actionable insights for every internal customer, refining and refreshing it along the way to ensure that it is as relevant as possible.

It's like they take the most powerful telescope imaginable and look for a speck of dust on the moon. “Here you go, this precise set of data will prove that you are right.”

The success of Big Data initiatives (to a large extent) comes in the ability to drill down from the planetary level to the sub-atomic level. It’s all about getting to those small insights that would never have appeared had you not started large and refocused, refocused, and refocused. Of course, this doesn’t mean that the bigger trends are not relevant, but we have a tendency to view anything “large” with a certain amount of mistrust.

Somehow, we naturally think that “big” things have a bigger margin for error, although the assumptions that we made on the way to the smaller insights could equally have been flawed.

So, what do we trust more — “big” things or “small” things?

Something tells me that we actually trust small things more, but I am very happy to hear the inevitably differing views of the readers.

I have a suspicion that when data science professionals talk about “Big Data” with their colleagues, the first reaction is for their eyes to glaze over and they automatically expect not to understand it. “It’s ‘big,’ and it needs a team of Ph.D.s to analyze it, so how would I possibly get my head around it?” If, on the other hand, there were a more accessible adjective such as small or tiny in front of the word “data” then maybe the end-clients would feel happier exploring it? Maybe I am overthinking things. For me, when something is described as small, it seems that bit more manageable.

Whatever the branding, Big Data is taking over our lives, both at work and at home. And the more we all seek to explore it, the more value we realize that it holds. The distillation process from large to small is key in many decision-making processes, and there are of course many potentially flawed assumptions that we can make along the way. But it is always possible to go back and correct those assumptions. Getting to “small data” from “big data” is the key for most of us in our lives, but we only do it if we are not daunted by the scope of the initial first few decisions.

We live in a data-rich society. If we think that the data is too big to mean anything for us, we are mistaken. It is remarkably easy to turn it into small, actionable data, despite the “Big Data” moniker that follows it around.

Big data Data science

Published at DZone with permission of Matthew Reaney. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • [DZone Survey] Share Your Expertise and Take our 2023 Web, Mobile, and Low-Code Apps Survey
  • Fixing Bottlenecks in Your Microservices App Flows
  • How To Create a Failover Client Using the Hazelcast Viridian Serverless
  • Microservices 101: Transactional Outbox and Inbox

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: