What does “enterprise grade” mean really?
A triangle model to deal with an ever evolving thought technology
#uptime14, 21 ...
2
Michael Coté
Research Director, Infrastructure Software
cote@451research.com
@cote – http://cote.io
Responsible for syst...
3
The Bastard Enterprise Iron Triangle Model
Configurablity Reliablity
Serviceablity
(You know the drill:)
You can pick two
4
There’s a lot of
re-writing and
re-platforming
ahead of us
5
Legacy…New…
Not seen here: white-collar toolchains
Sources: 451 HCTS NA 2013 conference; Chris Dancy.
Companies are beco...
6
To meet the needs of software, cloud is being deployed
17% 17%
19%
22% 22%
29%
32%
34%
40% 40% 39% 40% 41%
23%
29%
32%
2...
7
54% of early DevOps teams would like to deploy more
frequently, with 48% already deploying 30 days or less
Findings:
• 5...
8@swardley
9
So…what does
“enterprise
grade” mean
anyway?
10
We know it has something to do with being an “adult”…
Source: Twitter conversation, 30 April 2014.
11
“-ilities”: functionality, capabilities, robustness, auditable…
Source: Twitter conversation, 30 April 2014.
12
Business/IT Alignment, until your eyes bleed
13
The predictably snarky…
Source: Twitter conversation, 30 April 2014.
14
Defining the
triangle’s points
& their
problems
15
The Bastard Enterprise Iron Triangle Model
Configurablity Reliability
Serviceablity
16
Serviceablity – “a lot of effort went into making this
effortless”
• The more customization, the harder it is the manag...
17
Problem: a good admin is hard to find
22%
26%
19%
39%
29%
Feature creep (new requirements
are added inside each cycle,
...
18
Configurablity – getting exactly what you want incurs
“infrastructure debt”
• Each traditional enterprise
application i...
19
Problem: pets vs. cattle
Source: Gavin McCance at CERN in 2012, or maybe Bill Baker, via Noah Slater.
20
62%
49%
49%
2%
2%
5%
6%
3%
5%
4%
3%
7%
1%
7%
26%
27%
28%
15%
2H '13
2H '12
2H '11
Cattle management tools are on the ma...
21
Even in the mainstream DevOps world, adoption is early
Custom written build
scripts
38%
Golden Images
24%
Third party i...
22
Reliability – “it works!” all depends on the requirements
• Keeping up with the 9’s –
uptime vs. “works” time
• What re...
23
Problem: we’re used to building cathedrals
Source: ”The 6 Requirements of Enterprise-grade OpenStack, part 1,” Randy Bi...
24
Problem: GRC is, largely, people. Good luck with that.
Source: ”The 6 Requirements of Enterprise-grade OpenStack, part ...
25
What’s missing? For one thing: price…
Configurablity Reliability
Serviceablity
Thanks! @cote | cote@451Research.com | +1-512-795-4037
Upcoming SlideShare
Loading in...5
×

What Does "Enterprise Grade" Mean, Really?

1,098

Published on

For the lunch time talk at #uptime14.

Clearly, consumer tech and cloud offerings are performing at enterprise-grade scale and reliability. The next time someone tells me otherwise I'll just ask them how many times their email or VoIP has worked perfectly over the past year. I mean, Twitter has two factor authentication at this point, and the NSA spies on everything it seems, so we're on thin differentiation ice if "enterprise" is all that's holding us back from the unwashed public cloud barbarians. Still, there's a distinct feeling that there's something missing from cloud, DevOps, and new types of IT delivery ... something "enterprise." What are these things? Is it just literal and metaphoric paperwork that needs to be filled out for compliance, or is there something more that makes something "enterprise grade"?

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,098
On Slideshare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
9
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • How this is effecting industries:

    # Wall Street - from people to computers

    # Retail - from paper to computers, Square, Uber

    # Healthcare - from paper to computer

    # Consumer IoT and such stuff (more or less obvious)

    # All that white-collar toolchain stuff (Office, etc.) not here, but a big deal, obviously.
  • Grown-ups, adults, etc.
  • Functionality, capabilities, robustness.
  • Aligned to business…whether people like it or not
  • The other problem is infrastructure debt: doing too much that’s different, which leads to the next corner…
  • 20
  • What Does "Enterprise Grade" Mean, Really?

    1. 1. What does “enterprise grade” mean really? A triangle model to deal with an ever evolving thought technology #uptime14, 21 May 2014 @cote | cote@451Research.com
    2. 2. 2 Michael Coté Research Director, Infrastructure Software cote@451research.com @cote – http://cote.io Responsible for systems management, application development, cloud software, and misc. “infrastructure software” agenda. Before 451 I worked Dell in corporate strategy/M&A for software & cloud; as an analyst for 6+ years at RedMonk; software developer for 10+ years.
    3. 3. 3 The Bastard Enterprise Iron Triangle Model Configurablity Reliablity Serviceablity (You know the drill:) You can pick two
    4. 4. 4 There’s a lot of re-writing and re-platforming ahead of us
    5. 5. 5 Legacy…New… Not seen here: white-collar toolchains Sources: 451 HCTS NA 2013 conference; Chris Dancy. Companies are becoming “software defined businesses”
    6. 6. 6 To meet the needs of software, cloud is being deployed 17% 17% 19% 22% 22% 29% 32% 34% 40% 40% 39% 40% 41% 23% 29% 32% 29% 29% 29% 31% 0% 5% 10% 15% 20% 25% 30% 35% 40% 45% Jan-11 Apr-11 Jul-11 Oct-11 Jan-12 Apr-12 Jul-12 Oct-12 Jan-13 Apr-13 Jul-13 Oct-13 Jan-14 Corporate Market: Public and Private Cloud Usage (Private not tracked until Jul 2012) % using public cloud % using private cloud Source: A total of 1,137 respondents involved in their company's IT buying decisions participated in the January 8-27 survey, including 470 whose company currently use public cloud. ChangeWave Research is a service of 451 Research, from "Corporate Cloud Computing Trends," 451's ChangeWave, Feb 11, 2014.
    7. 7. 7 54% of early DevOps teams would like to deploy more frequently, with 48% already deploying 30 days or less Findings: • 51% cite business and strategy drivers: competitive, business productivity, revenue • 49% cite technology functionality, new feature sets, reduced development costs Source: 451 DevOps Study, 1Q2014. n=201 DevOps-minded individuals. 10% 12% 14% 18% 22% 23% Competitve pressures Reduce development cost Improved functionality Business revenue demands Deliver new features to users Business productivity demands Of these drivers, which one os the most significant driver of demand for reducing release cycles
    8. 8. 8@swardley
    9. 9. 9 So…what does “enterprise grade” mean anyway?
    10. 10. 10 We know it has something to do with being an “adult”… Source: Twitter conversation, 30 April 2014.
    11. 11. 11 “-ilities”: functionality, capabilities, robustness, auditable… Source: Twitter conversation, 30 April 2014.
    12. 12. 12 Business/IT Alignment, until your eyes bleed
    13. 13. 13 The predictably snarky… Source: Twitter conversation, 30 April 2014.
    14. 14. 14 Defining the triangle’s points & their problems
    15. 15. 15 The Bastard Enterprise Iron Triangle Model Configurablity Reliability Serviceablity
    16. 16. 16 Serviceablity – “a lot of effort went into making this effortless” • The more customization, the harder it is the manage and have it still work • If it’s always breaking, it’s not easy to manage – cf. fire-fighting • You’ll need a lot of good people for all those servers… Company Admin to Server Ratio Facebook 1:20,000 Highly customized, old days 1:60 “Cookie Cutter,” old days 1:150 2012/2013 TheInfoPro estimates 1:99 physical servers 1:142 virtual servers Pre-vBlock switch 12 admins for equivalent kit vBlock 3 admins to 1 vBlock Sources: Facebook from 2013 Delfina Eberly talk; "How Many Administrators are Enough?" Mark Verber, 1991 & 2008; vBlock from 451’s Peter Christy; effort for effortlessness from Mark Pilgrim.
    17. 17. 17 Problem: a good admin is hard to find 22% 26% 19% 39% 29% Feature creep (new requirements are added inside each cycle, lengthening the time to release) An inefficient process: Hand-off from development to test, to security etc. Lack of tools or inefficient tools for Release management, Log management, etc. Human resource constraints (can't hire enough skilled people so we bottleneck on those we have) Number and complexity of environments – Cloud, On- premises, Virtual and Physical DevOps: What is holding you back from reducing release cycles? Source: 451 Data Cloud Computing – Wave 6 ; 451 DevOps Study, Winter 2014. n=201 DevOps-minded individuals. 1% 1% 1% 1% 2% 2% 4% 5% 5% 6% 11% 12% 15% 18% 19% 37% 1% 15% 10% 10% 37% 10% 16% Building Service Catalog Cloud Performance Issues Integration Network Issues Legacy Systems/Applications Technology Immaturity Contractual Issues Internal Organizational Issues Trust (Visibility and Reliability) Data Management/Control Regulation/Compliance Security Policies Organization/Budget People/Time Vendor Selection/Offerings/Cost… Buy-in/Resistance to Change 1H '13 2H '13 Cloud: Non-IT Roadblocks
    18. 18. 18 Configurablity – getting exactly what you want incurs “infrastructure debt” • Each traditional enterprise application is a one off, requiring care and feeding • Here come the LDAP clowns and Mr. MDM • Conway’s infinite pizza team • New automation tools make software-based, API-heavy assets much more agile
    19. 19. 19 Problem: pets vs. cattle Source: Gavin McCance at CERN in 2012, or maybe Bill Baker, via Noah Slater.
    20. 20. 20 62% 49% 49% 2% 2% 5% 6% 3% 5% 4% 3% 7% 1% 7% 26% 27% 28% 15% 2H '13 2H '12 2H '11 Cattle management tools are on the map, but pets rule Source: Servers & Virtualization – Wave 13 Left Chart, n=180. Top Right Chart: 2H '11, n=108; 2H '12, n=175; 2H '13, n=180. Bottom Right Chart: 2013 vs. 2012, n=177; 2014 vs. 2013, n=177. The 'implementation' chart use the same legend as the vendor chart. Prior to 2H '12, 'Don't Know' responses were removed from calculations. Bottom Left Chart, Puppet Labs, n=70; Opscode (Chef), n=33; CFEngine, n=32; ComodIT, n=9. 0% 5% 10% 15% 20% 25% 30% 35% OpenStack VMTurbo Cisco Dell Puppet Labs IBM Homegrown HP Microsoft VMware In Use Now In Pilot/Evaluation (Budget Has Already Been Allocated) Near-term Plan (In Next 6 Months) Long-term Plan (6-18 Months) Past Long-term Plan (Later Than 18 Months Out) Not in Plan Don't Know 12% 16% 30% 3% 4% 22% 12% 13% 10% 22% 12% 22% 13% 56% 61% 50% 43% ComodIT Opscode (Chef) CFEngine Puppet Labs Extremely Likely Very Likely Somewhat Likely Minimally Likely Not at All Likely Implementation RoadmapVendor Implementation If Aware, Likelihood of Use a Vendor
    21. 21. 21 Even in the mainstream DevOps world, adoption is early Custom written build scripts 38% Golden Images 24% Third party install programs 20% Automation tools 16% Other 2% When designing and writing your software, how do you model and specify how the application should be deployed? Source: 451 DevOps Study, Winter 2014. n=201 DevOps-minded individuals.
    22. 22. 22 Reliability – “it works!” all depends on the requirements • Keeping up with the 9’s – uptime vs. “works” time • What regulations do you need to comply with? • How many full-blown transactions do you actually need? Source: OpenStack Summit, May 2014, @larryameyer.
    23. 23. 23 Problem: we’re used to building cathedrals Source: ”The 6 Requirements of Enterprise-grade OpenStack, part 1,” Randy Bias, April 2014; "Lean Startup Meets Lean Development," Erik Huddleston.
    24. 24. 24 Problem: GRC is, largely, people. Good luck with that. Source: ”The 6 Requirements of Enterprise-grade OpenStack, part 1,” Randy Bias, April 2014.
    25. 25. 25 What’s missing? For one thing: price… Configurablity Reliability Serviceablity
    26. 26. Thanks! @cote | cote@451Research.com | +1-512-795-4037
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×