Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

What Can DevOps Learn from Formula 1?

An old presentation from 2012 that I delivered at QCON. Somewhat relevant in today's world of Continuous Delivery.

  • Loggen Sie sich ein, um Kommentare anzuzeigen.

  • Gehören Sie zu den Ersten, denen das gefällt!

What Can DevOps Learn from Formula 1?

  1. 1. Dev OPS Stephen Burton,Tech Evangelist @BurtonSays What can DevOps Learn from F1?
  2. 2. • App Support • Developer • Systems Engineer • Pre-Sales • Product Management • Tech Evangelist About Me
  3. 3. 2011 Formula 1 World Champion SebastianVettel Who is this?
  4. 4. • 20 Races on the World Calendar • 12Teams, 24 Cars & Drivers • Cost is ~$7.5 Million per car • Spend $75 - $300 Million per year • 0-100-0 in < 5 seconds Formula 1
  5. 5. • F1 car has 80,000 components,1KM wiring &100+ sensors • 99.9% assembled correctly still means 80 POF’s • Monaco GP - Manholes are welded down • Brakes on F1 Car is like hitting a brick wall at 200mph (5G) • Downforce a baby elephant sitting on drivers head Interesting F1 Facts
  6. 6. “DevOps is about being agile,
 and going from
 A-Ha to Cha Ching
 as quickly as possible” John Willis
 DevOps Evangelist Why F1 and DevOps?
  7. 7. Innovation. Agility. Change.
  8. 8. Simple?
  9. 9. Hidden Complexity
  10. 10. Cutting Edge Technology
  11. 11. Cool Innovation
  12. 12. Simple?
  13. 13. Active Directory Tibco BW 3rd Party Web Service Oracle Cassandra Tomcat Tomcat JBoss ASP.NET 3rd Party Web Service SQL Server 3rd Party Java App JBoss JDBC SOAP ADO.NET HTTP SOAP SOAP LDAP ADO.NET THRIFT JMS THRIFT JMS HTTP Hidden Complexity
  14. 14. REALLY Really.
  15. 15. Really. Really.
  16. 16. Seriously.
  17. 17. What you can’t see...
  18. 18. Cool Integration
  19. 19. SUCCESS IN FORMULA 1 is Winning Races Success.
  20. 20. Ideas & Agility Wins Races
  21. 21. Dev Developers want Agility & Change OPS Operations want Availability & Stability WHAT IS SUCCESS FOR DEVOPS ?
  22. 22. COMPARINGTEAMS Formula 1 •Driver •Sponsors •Architects •Designers •Engineers •Testing •Operations •Support Applications •End User •Business •Architects •Designers •Developers •Testing •Operations •Support
  23. 23. MANAGING CHANGE ISN’T EASY Design > Build >Test > Deploy > Support Slowdowns Outages Mis-configuration Bottlenecks Bugs End User Complaints Business Requirements Project Plans More Business Requirements
  24. 24. CHANGE Doesn’t Happen OvernightThough
  25. 25. Change or Your Competition Will
  26. 26. • Cars Evolve • Up to 30 new parts per race F1 Teams Collaborate •Engineering • Aero, Engine,Transmission, .... •Operations • Mechanics,Telemetry, Pit Crew
  27. 27. Change is Constant
  28. 28. Develop Test SupportDeployDesign Operations work hand in hand with Engineering Race Weekend Formula 1 Lifecycle
  29. 29. MEASURING SUCCESS • Downforce • Performance • Reliability • Race Wins Telemetry & Monitoring Driver Results Monitoring is critical to Managing Change
  30. 30. End User Experience is Critical
  31. 31. Monitoring is also Critical
  32. 32. Measure Impact
  33. 33. The NOC
  34. 34. MONITOR & MANAGE IMPACT OF CHANGE Fast Slow Fail
  35. 35. Tools are Important
  36. 36. SO, DOYOU KNOW HOW FAST AND RELIABLE YOUR CODE IS IN PRODUCTION? <1% of Developers actually do
  37. 37. CODE CAN BE FUNCTIONALLY PERFECT Text But how Fast and Reliable will it be?
  38. 38. Concurrency DataVolume Resource 3 Things
 Impact Application Performance
  39. 39. DEV DataVolume ResourceConcurrency Very Fast QA/TEST DataVolume ResourceConcurrency Fast PRODUCTION DataVolume ResourceConcurrency ? THE PROBLEM
  40. 40. F1TESTING • 3 Pre-seasonTests (Integration & Soak testing) • 1 Mid-seasonTest (For Ferrari to catchup) • WindTunnel & Simulator (Unit & Functional & LoadTesting) • Race Weekends (ProductionTesting)
  41. 41. HANDS UP IFYOU DO PERFORMANCE TESTING ON EVERY RELEASE (Its tough with Agile cycles)
  42. 42. SUCCESS ISN’T HANDING OVER A RELEASETO OPS DEPLOY ME
  43. 43. GIFTS CAN HAVE SURPRISES NOBODY LIKES SURPRISES
  44. 44. DEV SUCCESS ISN’TTHE APP LASTING 1 HOUR IN PRODUCTION
  45. 45. • Ops has a 48 hour warranty period with Dev • If the App experiences consistent slowdowns or outages • AllTickets get re-assigned to Development A DevOps Warranty?
  46. 46. REAL-LIFE SURPRISESWhen Things go Wrong
  47. 47. BLUE - Concurrency (Trx/min) GREEN - Avg ResponseTime RED - Resource (CPU %) Dealing with Spikes
  48. 48. BLUE - Concurrency (Trx/min) GREEN - Avg ResponseTime Not Dealing with Spikes
  49. 49. T Po Po T Production Ground to a halt for 2 hours And again the next day Who owns JVM Configuration? Ops or Dev? Not Learning from Failure
  50. 50. Whose responsible for this? Ops? Bad Implementation
  51. 51. Whose responsible for this? Ops? Missing Configuration
  52. 52. Whose responsible for this? Ops? Inefficient Code
  53. 53. Root Cause: Cache wasn’t thread safe 46,463 Checkouts in the Day 2,492 were impacted Avg. $100 per Checkout Cost of Deadlock: ~ $249,000 Code Deadlock
  54. 54. IMAGINE ENGINEERS WITH NO RACEVISIBILITY Develop Test SupportDeployDesign Car would never win races or finish Race Weekend
  55. 55. Before After
  56. 56. Before After
  57. 57. • # Agile Releases or % Availability is pointless • End User Experience? • BusinessTransactionThroughput? • MTBF and Business Impact? DevOps Need Common Goals
  58. 58. • Feedback Loop from Ops to Dev • Share Goals,Tools & Metrics • Continuous Improvement • Learn from Failure • Win and LooseTogether Lessons Learned •Don’t write slow SQL Queries •Remember to use caching •Don’t rely on ORM •Assume everything will fail •Logging everything is not a good idea •Remember to do performance testing DevOps - Collaborate & Learn
  59. 59. • Define Success • Embrace Change, don’t fear it • Monitor, Measure and Manage Impact • Learn from Failure • Have Fun and remember Top Tips for DevOps
  60. 60. DevOps is about Team Work
  61. 61. + Visit the AppDynamics Booth FreeT-shirt Free Application Monitoring in Production www.appdynamics.com
  62. 62. We’re Hiring!

×