Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Beyond the Buzzwords

388 views

Published on

Beyond the Buzzwords - Duncan Winn, Keith Strini, Sean Keery
Originally delivered at Cloud Foundry Summit Europe 2017 Basel Switzerland October 11, 2017

Published in: Technology
  • You can hardly find a student who enjoys writing a college papers. Among all the other tasks they get assigned in college, writing essays is one of the most difficult assignments. Fortunately for students, there are many offers nowadays which help to make this process easier. The best service which can help you is ⇒ www.WritePaper.info ⇐
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Tattoo surgery too expensive? Lemon + this ingredient can take it off, Safe, effective, and inexpensive. ▲▲▲ https://bit.ly/2TliUmG
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Beyond the Buzzwords

  1. 1. Beyond The Buzzwords Duncan Winn | Platform Engineering | @duncwinn Sean Keery | Minister of Chaos | @zgrinch Keith Strini | Federal Practice Lead | @pivotal
  2. 2. IF WHAT
  3. 3. What if….
  4. 4. Cloud Computing Containers Agile DevOps CI/CD Platform Operations Microservices Cloud Native
  5. 5. Cloud Native CI/CD Cloud AgileMicroservices Platform Operations ContainersWhat is the VALUE?
  6. 6. VALUE? WHY QUANTIFY
  7. 7. VALUE? WHAT IS
  8. 8. verb Estimate the monetary worth of (something): Hard ROI • Removing Spend • Hardware / Middleware / OS Reduction • Automation What is Value noun The importance, worth, or usefulness of something • Faster Time to Market • Innovation • Delighted Customers
  9. 9. Effective Use of CAPEX Eliminating technical debt earlier, validated features, continuous product evolution reflecting changing user base ● Data driven decisions ● Higher customer spend ratio per investment dollar ● Lower overall subscription churn ● Less “restarts” more evolution Continuous Experimentation Reducing the risk of building the wrong thing while nimbly changing direction ● Distributed Tracing/Shared Context (Fast Feedback) ● Identify & test assumptions ● Direct feedback to Design/CFO/CEO ● Lower CAPEX per hypothesis Cloud Native Enablement Cloud Native Org PRACTICES PRACTICES Waste Reduction Leveraging a Platform with cloud-ready workloads to remove delivery constraints ● Paired Programming ● CI/CD and better QA/TDD ● Rel-Eng Intelligence ● Automated Resilient Ops Operations + App Transformation PRACTICES Cloud Native ROI Continuum
  10. 10. REDUCTION WASTE
  11. 11. Code Deploy Prod Support Work Flow Value Stream Mapping Request Delivery
  12. 12. Muda Type I Non-value added activity, necessary for end customer Muda Type II Non-value added activity, unnecessary for end customer What is muda - 無駄 Any process that consumes more resources than needed
  13. 13. DevOps Principles Networkin g Admin Security Auditor QA Perf Test Storage Admin App Architect Project Manager Sys Admin IaaS Admin
  14. 14. DevOps with Cloud Foundry
  15. 15. Stability ● Blue/Green / Canaries ● Resilience ● Self Healing Speed ● Env Setup ● Release / Day 2 Automation Scalability ● Dynamic Routing ● On Demand / Auto Elasticity Security ● Rotate ● Repair ● Repave Savings ● Resource Consolidation ● Software Reduction ● Automation
  16. 16. Request Delivery Lead Time Value Added Process Time Non-Value Added Activities (TYPE 2) Lead Time
  17. 17. PROVISION ENV VM/OS Middleware CODE Develop Func Test RELEASE CI/CD Test/Stage DAY 2 OPS Monitor Patch Scale Request Delivery Lead Time Value Added Process Time Request Delivery Lead Time Value Added Process Time Request Delivery Lead Time Value Added Process Time Request Delivery Lead Time Value Added Process Time
  18. 18. ~30 to 50 people just patching VMs
  19. 19. Stability Speed Scalability
  20. 20. VALUE MEASURING
  21. 21. Dickerson's Hierarchy of Reliability
  22. 22. An SLI is a quantitative measure of some aspect of the level of service that is provided Service Level Indicators
  23. 23. An SLO is a target value, or range of values, for a service level that is measured by an SLI Service Level Objectives
  24. 24. SLAs are a contract with your users that includes consequences of meeting (or missing) the SLOs they contain Service Level Agreements
  25. 25. VALUE TEST DRIVEN OPERATIONS
  26. 26. SLIs and SLOs are crucial elements in the control loops used to identify systemic value: Monitor and measure the system’s SLIs. Compare the SLIs to the SLOs, and decide whether or not action is needed. If action is needed, figure out what needs to happen in order to meet the target. Take that action. Review SLO’s. Continuous Experimentation
  27. 27. Software Value Map
  28. 28. VALUE AVOID WASTE
  29. 29. Our Service Level Agreement will be “Real Time Readiness of the Platform.” Our Service Level Indicators and Objectives: Cell Rep Time Synch < 5m BBS Time to Run LRP Convergence > 10m Auctioneer App Instances Placement Failures > 0.5 Auctioneer Task Placement Failures > 0.5 Waiting or Delays Latency
  30. 30. Our SLA will be “Proactive Security Mitigation.” Our Service Level Indicators and Objectives: Number of Authn Errors > 10 attempts Number of Failed Logons > 4 attempts Number of Forbidden SSH Sessions > 2 Defects Errors
  31. 31. Our SLA will be “Proactive Scaling of the Platform.” Our SLI and SLO’s: Unhealthy Cells = 0 Remaining Memory - Cell Memory Chunks Available > 4 Remaining Memory - Overall Memory Available > 4 Over-production or Extra Features 35 Saturatio n
  32. 32. Transportation or Handoffs Traffic Our SLA will be “Proactive Scaling of our Apps.” Our SLI and SLO’s: Router Throughput > 10000 rps # of Request per Application Instance > 1000 rps # of Request per Application Function > 100 rps
  33. 33. Continuous Experimentation Cycles
  34. 34. Effective Use of CAPEX Eliminating technical debt earlier, validated features, continuous product evolution reflecting changing user base ● Data driven decisions ● Higher customer spend ratio per investment dollar ● Lower overall subscription churn ● Less “restarts” more evolution Continuous Experimentation Reducing the risk of building the wrong thing while nimbly changing direction ● Distributed Tracing/Shared Context (Fast Feedback) ● Identify & test assumptions ● Direct feedback to Design/CFO/CEO ● Lower CAPEX per hypothesis Cloud Native Enablement Cloud Native Org PRACTICES PRACTICES Waste Reduction Leveraging a Platform with cloud-ready workloads to remove delivery constraints ● Paired Programming ● CI/CD and better QA/TDD ● Rel-Eng Intelligence ● Automated Resilient Ops Operations + App Transformation PRACTICES Cloud Native ROI Continuum
  35. 35. VALUE FUTURE
  36. 36. Company Objective 1 - Release Money: Acquire + Retain Customers - Key Result 1 - 40% Redux in OPEX - Key Result 2 - 20% more efficient use of CAPEX for new customer acquisition Company Objective 2 - Capture and Retain New Market Share - Key Result 1 - 3 new revenue generating products / quarter - Key Result 2 - 10% lower churn in new user base vs existing product churn What If?
  37. 37. EXPERIMENTATION CONTINUOUS
  38. 38. Effective CAPEX Expenditures ROIs TRUE VALUE
  39. 39. ADVENTURE CHOOSE YOUR OWN
  40. 40. Fundamentally changes product development - What if customer chose their own Adventure? Streaming (ABooks/Movies) Physical Media EPurchase (Physical Prod) Automated Rec Engine Manual Rec Engine No targeted ads Not Tailored Sales Tailored Sales Targeted Ads Automated Rec Engine Manual Rec Engine
  41. 41. Complex Assumption Validation via Distributed Trace Assumption 1 - 50% B/G - 100% B/G - 100% B/G - 50% B/G - 25% B/G - 50 % A/B Test B/G - 40% Assumption 3 - 0% Assumption 2 - 50% B/G - 60% B/G - 50% B/G - 25% B/G - 25% B/G - 50 % B/G - 33 % B/G - 33 % B/G - 33 %
  42. 42. SUMMARY TAKE AWAYS
  43. 43. Effective Use of CAPEX Eliminating technical debt earlier, validated features, continuous product evolution reflecting changing user base ● Data driven decisions ● Higher customer spend ratio per investment dollar ● Lower overall subscription churn ● Less “restarts” more evolution Continuous Experimentation Reducing the risk of building the wrong thing while nimbly changing direction ● Distributed Tracing/Shared Context (Fast Feedback) ● Identify & test assumptions ● Direct feedback to Design/CFO/CEO ● Lower CAPEX per hypothesis Cloud Native Enablement Cloud Native Org PRACTICES PRACTICES Waste Reduction Leveraging a Platform with cloud-ready workloads to remove delivery constraints ● Paired Programming ● CI/CD and better QA/TDD ● Rel-Eng Intelligence ● Automated Resilient Ops Operations + App Transformation PRACTICES Cloud Native ROI Continuum
  44. 44. Transforming How The World Builds Software © Copyright 2017 Pivotal Software, Inc. All rights Reserved.

×