Cookies help us display personalized product recommendations and ensure you have great shopping experience.

By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
SmartData CollectiveSmartData Collective
  • Analytics
    AnalyticsShow More
    sales and data analytics
    How Data Analytics Improves Lead Management and Sales Results
    9 Min Read
    data analytics and truck accident claims
    How Data Analytics Reduces Truck Accidents and Speeds Up Claims
    7 Min Read
    predictive analytics for interior designers
    Interior Designers Boost Profits with Predictive Analytics
    8 Min Read
    image fx (67)
    Improving LinkedIn Ad Strategies with Data Analytics
    9 Min Read
    big data and remote work
    Data Helps Speech-Language Pathologists Deliver Better Results
    6 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: The Argument For & Against Map/Reduce
Share
Notification
Font ResizerAa
SmartData CollectiveSmartData Collective
Font ResizerAa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Big Data > Data Visualization > The Argument For & Against Map/Reduce
Data Visualization

The Argument For & Against Map/Reduce

TonyBain
TonyBain
3 Min Read
SHARE

The last 24 months has seen the introduction of Map/Reduce functionality into the data processing arena in various forms.  Map/Reduce is a framework for developing scalable data processing functionality, and was popularized by Google (see this earlier post).

Pure players like Hadoop are starting to find their own niche, helped by organizations such as Cloudera.  However there has been a number of for & against arguments relating to Map/Reduce functionality inside the database.

These arguments are now really serving a moot point.  Customers have recognized value in Map/Reduce prompting some (b)leading edge database vendors to introduce such functionality into their platforms (primarily database vendors providing analytics platforms).  Even some of the database platform vendors who were very critical of Map/Reduce 12 months or so ago have softened their position, either embracing Map/Reduce or admitting that Map/Reduce does has benefits in some scenarios for large scale data processing and analytics.  If customers see the value of having Map/Reduce in the database and are excited by it, then I don’t want to spend any more time debating if it should be there or not.

Our attention …

More Read

Step Into the Smarter Planet Time Machine! For a little Friday…
Big Data Statistics in the Search for a Cure for MS
5 Best Practices for Extracting, Analyzing, and Visualizing Data
The 8 Laws of Dashboard Design: This Is Not an 80’s Rave
The Environmental Performance Index, Visualized with R

The last 24 months has seen the introduction of Map/Reduce functionality into the data processing arena in various forms.  Map/Reduce is a framework for developing scalable data processing functionality, and was popularized by Google (see this earlier post).

Pure players like Hadoop are starting to find their own niche, helped by organizations such as Cloudera.  However there has been a number of for & against arguments relating to Map/Reduce functionality inside the database.

These arguments are now really serving a moot point.  Customers have recognized value in Map/Reduce prompting some (b)leading edge database vendors to introduce such functionality into their platforms (primarily database vendors providing analytics platforms).  Even some of the database platform vendors who were very critical of Map/Reduce 12 months or so ago have softened their position, either embracing Map/Reduce or admitting that Map/Reduce does has benefits in some scenarios for large scale data processing and analytics.  If customers see the value of having Map/Reduce in the database and are excited by it, then I don’t want to spend any more time debating if it should be there or not.

Our attention needs to move along from debating if Map/Reduce is something we should have in our database toolset or not.  We now need to start thinking about how we use this new tool effectively and what new possibilities Map Reduce opens up.

Link to original post

Share This Article
Facebook Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

sales and data analytics
How Data Analytics Improves Lead Management and Sales Results
Analytics Big Data Exclusive
ai in marketing
How AI and Smart Platforms Improve Email Marketing
Artificial Intelligence Exclusive Marketing
AI Document Verification for Legal Firms: Importance & Top Tools
AI Document Verification for Legal Firms: Importance & Top Tools
Artificial Intelligence Exclusive
AI supply chain
AI Tools Are Strengthening Global Supply Chains
Artificial Intelligence Exclusive

Stay Connected

1.2kFollowersLike
33.7kFollowersFollow
222FollowersPin

You Might also Like

Are You Reporting What You Can?…Or What You Should?

6 Min Read

Lessons from F1 racing: Timely Decisions Get You on the Podium

6 Min Read

Seven Misconceptions about Data Quality

11 Min Read

Translating Awareness to Consideration Set in B2B

6 Min Read

SmartData Collective is one of the largest & trusted community covering technical content about Big Data, BI, Cloud, Analytics, Artificial Intelligence, IoT & more.

ai in ecommerce
Artificial Intelligence for eCommerce: A Closer Look
Artificial Intelligence
AI and chatbots
Chatbots and SEO: How Can Chatbots Improve Your SEO Ranking?
Artificial Intelligence Chatbots Exclusive

Quick Link

  • About
  • Contact
  • Privacy
Follow US
© 2008-25 SmartData Collective. All Rights Reserved.
Go to mobile version
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?