Strata Standards Stories: Different Stores For Different Chores

Has HDFS joined MapReduce in the emerging “legacy Hadoop project” category, continuing the swap-out of components that formerly answered the question “what is Hadoop?” Stores for data were certainly a focus at Strata/Hadoop World in NY, O’Reilly’s well-run, well-attended, and always impactful fall event. The limitations of HDFS, including its append-only nature, have become inconvenient enough to push the community to “invent” something DBMS vendors like Oracle did decades ago: a bypass. After some pre-event leaks about its arrival, Cloudera chose its Strata keynote to announce Kudu, a new columnstore written in C++, bypassing HDFS entirely. Kudu will use an Apache license and will be submitted to the Apache process at some undetermined future time.


Perspectives on Hadoop Part Two: Pausing Plans

By Merv Adrian and Nick Heudecker 

In the first post in this series , I looked at the size of revenue streams for RDBMS software and maintenance/support and noted that they amount to $33B, pointing out that pure play Hadoop vendors had a high hill to climb. (I didn’t say so specifically, but in 2014, Gartner estimates that the three leading vendors generated less than $150M.)

In this post, Nick and I turn from Procurement to Plans and examine the buying intentions uncovered in Gartner surveys.


–more in Gartner blog–

Perspectives on Hadoop: Procurement, Plans, and Positioning

I have the privilege of working for the world’s leading information technology research and advisory company, covering information management with a strong focus for the past few years on an emerging software stack called Hadoop. In the early part of 2015, that particular technology is moving from early adopter status to early majority in its marketplace adoption. The discussions and published work around it have been exciting and controversial, so in this post (and a couple to follow) I describe three interlocking research perspectives on Hadoop: procurement (counting real money actually spent); plans (surveys of intentions to invest) and positioning (subjective interpretations of what the first two mean.)

Procurement Perspective: Hadoop is a (Very) Small Market Today

–more on Gartner blog–



Hadoop Questions from Recent Webinar Span Spectrum

This is a joint post authored with Nick Heudecker
There were many questions asked after the last quarterly Hadoop webinar, and Nick and I have picked a few that were asked several times to respond to here.

–More on my Gartner blog

Which SQL on Hadoop? Poll Still Says “Whatever” But DBMS Providers Gain

Since Nick Heudecker and I began our quarterly Hadoop webinars, we have asked our audiences what they expected to do about SQL several times, first in January 2014. With 164 respondents in that survey, 32% said “we’ll use what our existing BI tool provider gives us,” reflecting the fact that most adopters seem not to want to concern themselves overmuch with the details.

–More on my Gartner blog

Oracle Hardware – No, The News is Not Good. (Yet.)

As an information management software analyst, I don’t spend a great deal of time looking at hardware, but when I look for a more holistic view, I occasionally check in with Gartner colleagues. Recently I had a few questions about Oracle’s hardware mix during inquiries, so I decided to check in with my colleague Errol Rasit about Gartner Quarterly Market Statistics, and find out how the hardware recovery I keep hearing about was going.  What I discovered surprised me, especially in light of the messages I hear from the vendor.

There is no “recovery.” It appears that the picture remains rather bleak, especially on the SPARC side.

— more on my Gartner blog —

Prediction Is Hard – Especially About the Future

OK, I admit it – I stole the title from a much smarter man. I thought that man was Yogi Berra, but maybe not – more about that at the end of this post.

Every year, Gartner issues a series of Predicts documents. This year I had the pleasure of doing one for my team on Information Infrastructure Technology. Now, I’m a software guy, and the team I’m on is all software people, so a document assigned to our team would typically be about – well, information software technology. But that would have missed the point rather dramatically, so I connected with a few colleagues and got their OK to use some of their predictions in the small set any document can include.

— more on Gartner blog —