Gartner Blog Network


Symposium Notes – Day One Features Hadoop

by Merv Adrian  |  October 18, 2016  |  Comments Off on Symposium Notes – Day One Features Hadoop

Gartner Symposium is always exciting, challenging and stimulating for analysts; we get to interact with many organizations in a brief time during 1on1 meetings scheduled based on our coverage. It offers an fascinating snapshot of what is on people’s minds – enough so that they have traveled to a conference in part to have that discussion.

Today was the first full day of the 2016 Symposium and over half of my meetings were about Hadoop. Combining data is a big focus – enriching existing data, often in DBMSs, with additional information from other sources to get a more accurate or complete picture. Many of the new sources were streaming ones, and confirmed my conviction that mixing data in motion with data at rest will be a key architecture in 2017.

Securing data in Hadoop and big data implementations came up several times. Security authorization needs to be well documented for reuse, also confirming a theme I see a great deal. As I noted in Rethink and Extend Data Security Policies to Include Hadoop, authorization for existing data must be reproduced for the new – unsecured – data entering from unknown and unvetted sources.

Today’s Symposium keynote featured some aggressive comments about the need to replace outdated legacy software, and several of my meetings covered software in versions as much as a decade old. Worse, it had often been left in place because of dependencies on applications that were not keeping pace with updates to DBMSs – even when the vendor of both offerings was the same. Customers need to expect more, and make changes when those expectations remain unmet.

This includes movement to the cloud, another recurring theme – some vendor portfolios are moving to the cloud at varying rates, creating challenges for stacks that need to reside both on premises and in the cloud. In another meeting, we covered the failure of some early customer tests of migration to the cloud to meet business requirements, despite assurances they would and strong vendor pressure to move now.  “Should we relax our requirements?” My response: remember that often salespeople are being incented to make you move, whether that is in your best interest or not. Be clear on your criteria, and don’t move until they are met.

Today I had 8 meetings – and 3 more that were cancelled. That is a fairly typical ratio – so many things are going on that attendees sometimes can’t make it. It’s a shame when they don’t notify our staff so other people could use the slot – some analysts’ entire calendar is filled, leaving some attendees unable to get a meeting. It’s doubly troubling when the missed meetings were with vendors who use the event as a chance to squeeze in another briefing. They get other opportunities, and in any case it’s not a very good venue, because we’re so overloaded it’s not likely that we will remember much that is pushed at us here. I’m looking forward to the next three days, and hoping for the calendar to stay full.

Category: analyst-relations  hadoop  cloud  dbms  gartner  industry-trends  security  

Tags: hadoop  hbase  spark  cloud  data-security  gartner  

Merv Adrian
Research VP
5 years with Gartner
38 years in IT industry

Merv Adrian is an analyst following database and adjacent technologies as extreme data transforms assumptions about what to persist as well as when, where and how. He also watches the way the software/hardware boundary… Read Full Bio




Comments are closed

Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.