The Five-Year Storage Scenario - Gartner - Dave Russell

The Five-Year Storage Scenario: Why Storage in 2018 Won't Look Like What's on the Floor Today
Dave Russell

Gap widening between tech and service lives
  • tech advantages
  • Life of storage increasing - e.g. 7 years for an array
  • Are the choices I am making today going to work in the future?
  • Stuck with what you buy as legacy
  • Constraints – time, people, money
The World in Five Years
  • Data growth – what does it look like; where does it reside
  • Application morphs
  • Smart Everything - sensors
  • Data Accessibility from anywhere, anytime, any device
CMO might wield more budget than the CIO

Changes affecting data
  • new options for where data is stored
    • Mobile and cloud computing
  • Global access and usage of data
  • Packaging and delivery models – convergence of compute, storage, network
  • Security problems – federated model; stitching together
Data Governance Changes
  • tension between personal privacy vs global accessibility 
  • Govt is getting more involved in data
  • Risk tolerance increases; corners cut; I will run the risk that someone catches me and pay the fine.
Economic and social issues force change
  • demographics --> age related computing
  • Terrorism and intl rivalries
  • Supply challenges – inability to meet storage demands

Storage Product Differentiation Compresses
  • functional advantages can be short lived
  • Non-product decision criteria increase in importance – implementation, acquisition, support
Key Storage Trends
  • software becomes the focus;  sw moves from enabler to driver
  • Info governance becomes critical and mainstream; IT enforces governance policies
  • Org changes; who owns, who selects, who manages? From specialist to concierge
  • Chief Digital Officer
2-3 Years out
  • technology is primary focus – sw defined storage
  • Commoditization of storage; object-based, public cloud, hadoop, openStack
  • Storage moves to the edge
  • Blending of backup and DR
  • Archiving and info governance gains importance
5+ Years out
  • Apps and data cohabitate
  • Does backup go away? Method to protect data built-in.
  • Performance no longer an issue
  • New roles emerge; does storage team go away?
  • More buying centers – shadow IT
Big Storage Vendors
  • Data moves to the cloud
  • More buying centers
  • Many possible outcomes
  • Scary to be big storage today – compressed differentiation
  • Can't sell on performance, availability or cost – good enough keeps getting better and better
The cloud could disintermediate the incumbent storage vendors. Hence their strategy to support cloud.
Cloud gateways become a feature in cloud storage.
The Amazonification of IT – they are willing to make pennies on IT services.

HyperScale Vendors
  • Amazon, Ebay, Facebook, Google, Yahoo
  • Trend setting so others follow
  • Next wave HyperScalers are Chinese – Baidu, Alibaba, Tencent, Sina
Some companies have an "open source first" policy which could spread to storage

Trends
  • Public Cloud
  • Hadoop and Open Stack
  • Pervasive Flash
  • Commonditization of Storage
  • SW defined Storage
Review and possibly disregard past design decisions
Make the right workload to the right tool

Best Practice
  1. create your data strategy with the future in mind
  2. Invite new emerging solutions to engage in your RFPs
  3. Link storage to the rest of IT and the business – storage remains the most opaque resource in the data center

Network is stateless, Storage has weight.

Comments

Post a Comment

Popular posts from this blog

Enterprise Architecture Inside Salesforce

Image
  Enterprise  Architecture Inside Salesforce Enterprise Architecture — How We Do It Internally The two words, “Enterprise Architecture”, elicit various reactions — everything from “ we tried that and it doesn’t work ” to “ we need that! ” to “ we have an effective EA practice ”. Unfortunately it is possible (even easy) to do Enterprise Architecture  incorrectly , with an approach that is lethargic, technology-first and theoretical — the classic ivory tower. (In Salesforce, the internal IT group reporting into our CIO is called “Business Technology” so you’ll see me use BT to refer to Salesforce IT) I lead the Salesforce Enterprise Architecture team within Business Technology and I’m often asked the following questions: how does Salesforce do Enterprise Architecture? why do you need Enterprise Architecture? how do you shift the conversation to business capabilities? Illuminate — The “How” of Salesforce Enterprise Architecture Let me start with the “HOW” first. Within Sales...
Read more

Illuminate - Business Model Exploration

Image
  Illuminate — Business Model Exploration One of our world-class Salesforce Enterprise Architects, Jonathan Laudicina ( https://www.linkedin.com/in/jonathan-laudicina/  ) has done amazing work on Business Model Exploration. I want to highlight some of his work and I think you’ll find it useful. As a reminder, Illuminate is the Enterprise Architecture Methodology that we use inside Salesforce as well as with our customers. The overall Illuminate methodology is depicted below. You will notice that Business Model Exploration is the first step in Illuminate. Business Model Exploration is the methodology we use with customers to articulate: External Forces pushing on the business Internal Forces pushing on the business Customer specific Business Model Canvas At the heart of Business Model Exploration is the Business Model Canvas. It is the place in which you capture key factors about a company’s specific value proposition, partners, customer segments, cost structure and revenue str...
Read more

5 Key Components of a Successful Enterprise Architecture Function

  5 Key Components of a Successful Enterprise Architecture Function 5 Key Components of a Successful Enterprise Architecture Function Creating and managing a successful Enterprise Architecture function requires a variety of different hard and soft skills. In addition, each company is different and the Enterprise Architecture function needs to calibrate and align itself to the specific company. However, there are five common features of a successful Enterprise Architecture function that are applicable to all companies. 1. Governance Enterprise Architecture (EA) requires governance, however not in the form of complex documents, forms or processes.  Definitely avoid EA being seen as the policy-enforcement team — people will avoid EA if the perception is that EA is a blocker.  The best governance starts with a simple, recurring dialogue across multiple functions facilitated by EA. I am always amazed at how valuable it is just to get cross-functional teams to  talk . Pick...
Read more