Now Playing Tracks

Top Technology Trends Impacting Information Infrastructure in 2013 According to Gartner

nosql:

Gartner, Inc. has identified the top technology trends that will play key roles in modernizing information management (IM) in 2013 and beyond, making the role of information governance increasingly important.

According to the PR announcement accompanying the report, there are 9 technologies in this list:

  1. Big Data
  2. Modern Information Infrastructure
  3. Semantic Technologies
  4. The Logical Data Warehouse
  5. NoSQL DBMSs
  6. In-Memory Computing
  7. Chief Data Officer and Other Information-Centric Roles
  8. Information Stewardship Applications
  9. Information Valuation/Infonomics

Notable technologies missing:

  1. RDBMS
  2. Data-oriented appliances
  3. Data-as-a-Service

    Note: the last two could be part of the larger category “Modern Information Infrastructure”, but without access to the report I cannot tell if they are part of it or not.

  4. Analytic databases.

  5. Data virtualization

    Note: Gartner touts the “Logical Data Warehouse” concept for a while and it superseeds analytic databases and data virtualization

  6. MDM.

    Note: I could see though this being included in the “Information Stewardship Applications” category

  7. Data visualization.

    Note: most probably this is part of the “Information Valuation/Infonomics” category.

I ended up wondering if there’s any data related technology left out from this list.

Original title and link: Top Technology Trends Impacting Information Infrastructure in 2013 According to Gartner (NoSQL database©myNoSQL)

Why Big Data Projects Fail

nosql:

Stephen Brobst of Teradata:

There are four primary reasons that big data projects fail:

  1. They focus on technology rather than business opportunities.
  2. They are unable to provide data access to subject matter experts.
  3. They fail to achieve enterprise adoption.
  4. The enterprise lacks the sophistication to understand that the project’s total cost of ownership includes people as well as information technology systems.

I tend to disagree with the last 3 points or at least not consider those as primary reasons.

Except the novelty of this new field and thus its inherent challenges of new technologies being used, I don’t think big data projects are any different to other projects. And their failures are caused by the same well known reasons. Maybe the only new one is the unreasonable expectations. But even this one doesn’t seem so new to me.

Original title and link: Why Big Data Projects Fail (NoSQL database©myNoSQL)

Hadoop Weaknesses and Where Teradata Aster Sees the Big Data Money

nosql:

An interesting post on Teradata Aster blog which is indirectly emphasizing the weaknesses of the Hadoop platform:

  1. Make platform and tools to be easier to use to manage and curate data. Otherwise, garbage in = garbage out, and you will get garbage analytics.
  2. Provide rich analytics functions out of the box. Each line of programming cuts your reachable audience by 50%.
  3. Provide tools to update or delete data. Otherwise, data consistency will drift away from truth as history accumulates.
  4. Provide applications to leverage data and find answers relevant to business. Otherwise the cost of DIY applications is too high to influence business – and won’t be done.

It’s difficult to argue against these points, but they are not insurmountable. I’d even say that once the operational complexity of Hadoop deployments will get simpler—I think the Apache community, Cloudera, and Hortonworks are already working on these aspects—, Hadoop will see even more adoption and with that contributions addressing points 2 to 4 will follow shortly.

Yet another interesting part of the post is the two “equations” describing the two environments:

big clusters = big administration = big programs = big friction = low influence (Hadoop)
big data = small clusters = easy administration = big analytics = big influence (ideal/Teradata Aster)

I think these are revealing how Teradata Aster is positioning their solutions and where they see themselves making money in the Big Data market. It goes like this: “we can make a lot of money if we offer a platform with lower complexity and operational costs and higher productivity leading to better business results”. This is a sound strategy and the competitors from the Hadoop space should better focus on these same aspects which are essential to wide adoption.

Original title and link: Hadoop Weaknesses and Where Teradata Aster Sees the Big Data Money (NoSQL database©myNoSQL)

To Tumblr, Love Pixel Union