Comments for Merv Adrian's IT Market Strategy IT Industry trends: technology, products, competition and the research industry. Fri, 05 Dec 2014 21:11:54 +0000 hourly 1 Comment on Hadoop Is A Recursive Acronym by Ranko Mosic Mon, 13 Oct 2014 14:23:02 +0000 I don’t think name matters that much. What is happening is incredibly easy data management oriented MPP on commodity platforms, and incumbents are not part of it, except as extend and embrace. What it will contain will change forever. Oracle RDBMS also stood for many things.

Comment on IBM’s BAO Initiative Will Change the Landscape, But More Is Needed by Merv Adrian Sun, 26 May 2013 18:05:55 +0000 I see it as a way to keep my name out there. It’s an unfortunate reality that some lifting will happen. It hasn’t been enough of an issue that i have pursued it.

Comment on Sand Technology a Risky Bet by Jennifer Dawn Wed, 22 May 2013 19:09:51 +0000 Boy, these guys sure imploded, didn’t they?

Comment on You Know You Have Big Data When…(Humor) by ksankar Tue, 12 Mar 2013 07:26:35 +0000 You know you have big data when ….
… Your HOURLY log data exceeds the size your ENTIRE product catalogue
… Instead of a small ETL window you have a small transaction window and the rest is used by ETL processes
… You apply CAP theorem to your DBAs

Comment on You Know You Have Big Data When…(Humor) by Paige Roberts Sun, 10 Mar 2013 23:40:07 +0000 You know you have big data when …

your data center has it’s own zip code.

your analytics query response time is measured in generations.

running your weekly update report takes 10 days.

your data visualization works best on a billboard.



Comment on 2013 Data Resolution: Avoid Architectural Cul-de-Sacs by Merv Adrian Thu, 27 Dec 2012 22:24:10 +0000 In reply to Richard Hackathorn.

Thanks! I think it’s fair to say it’s difficult and expensive but not impossible, though in practical terms there may be little difference.

Comment on 2013 Data Resolution: Avoid Architectural Cul-de-Sacs by Richard Hackathorn Thu, 27 Dec 2012 20:16:10 +0000 Like your title as ‘archectural cul-de-sac’. This implies that one can turn around and exit the same way as entering. Maybe an ‘architectural black hole’ is more appropriate since one can not exit once pass the event horizon!

Comment on Bio by Merv Adrian Wed, 28 Nov 2012 03:28:21 +0000 #comment-8190 In reply to Alex Plavocos.

And I learned a lot about it from you, my first mentor. Great to hear from you!

Comment on Bio by Alex Plavocos Tue, 27 Nov 2012 16:26:22 +0000 #comment-8188 Merv,
So great to catch up with you and your career. When we were at Information Builders it was part of your foundation that you worked with the analyst community. So glad to see how far you have come.
Alex Plavocos

Comment on Migrate From Mainframe? To What? by Joe Clabby Sun, 04 Nov 2012 09:47:03 +0000 To bouffon’s comments, I must admit that I’m a bit dumbfounded. Mainframes are outdated technology? Have you looked at which system offers the fastest processor in the world with the most onboard memory cache? Do you know that mainframes are the only commercial servers to have attained EAL Level 5+ technology? Are you aware that mainframe virtualization is a decade ahead of x86 in terms of features/functions and managability? And, as for cost, are you aware that it can cost almost $1.5 million less to run the same banking application on a mainframe as compared with an x86 environment (see my report here for further details: Also, when your reading it, consider that I did not include how much more it costs to power an x86 server farm, nor did I include the hundreds of thousand of additional dollars it would cost to manage that farm. Nor did I account for all of the additional cable (and associated labor to deploy the physical plant).

Please go back and read Craig Mullin’s comment above. In the end it is all about which workloads execute best on which servers. As Craig puts it: “if you plan to plough a field and you have a choice between an ox (mainframe) and 32 chickens (intel servers) which would you choose?”

Finally, I discuss the differences between mainframes, RISC, and x86 environments in great detail on my new site: What you will learn on this site is that some workloads belong on x86, some on RISC, and some on mainframes because each server has characteristics that support workloads differently. Further, there are very significant cost implications to choosing the wrong server. To your original point: x86 architecture does not do every job most optimally — so to argue that a mainframe is old and expensive, and that x86 is au currant and exciting, the way of the future, and the only choice the industry needs — is just plain tiresome…

  • 探球网足球比分