Upgrade to Pro — share decks privately, control downloads, hide ads and more …

WHO OWNS CHAOS?

777bc656cb5c276519c2d52951d6ebca?s=47 Chaos Conf
September 26, 2019

WHO OWNS CHAOS?

Joyce Lin, Postman

777bc656cb5c276519c2d52951d6ebca?s=128

Chaos Conf

September 26, 2019
Tweet

More Decks by Chaos Conf

Other Decks in Technology

Transcript

  1. PRESENTED BY Who is responsible for chaos? Chaos Conf Joyce

    Lin Lead Developer Advocate, Postman @petuniaGray @postmanClient
  2. Joyce Lin Lead Developer Advocate, Postman Postman is an API

    Development Environment (ADE) used by more than 8 million people. For many teams, Postman is an everyday tool that helps people work with APIs more efficiently. @petuniaGray
  3. TITL E 250 million + APIs 400,000 + companies 8

    million + developers @petuniaGray
  4. Who is responsible for chaos? @petuniaGray

  5. Known Chaos Engineering tools and engineers @petuniaGray

  6. Which job titles are doing chaos? @petuniaGray

  7. @petuniaGray By Job Title

  8. It boils down to who gets paged - if that’s

    an SRE or Ops team they have the most incentive to start doing this work and making their lives better. - Kolton Andrus, CEO at Gremlin @petuniaGray
  9. Responsibilities •  Chaos specialists @petuniaGray

  10. Responsibilities •  Chaos specialists •  Deployment and uptime @petuniaGray

  11. Responsibilities •  Chaos specialists •  Deployment and uptime •  Incident

    management @petuniaGray
  12. Responsibilities •  Chaos specialists •  Deployment and uptime •  Incident

    management •  Domain knowledge experts @petuniaGray
  13. Responsibilities •  Chaos specialists •  Deployment and uptime •  Incident

    management •  Domain knowledge experts •  * Testing in Production @petuniaGray
  14. Roles •  Site Reliability engineers •  Production engineers •  DevOps

    engineers •  InfoSec engineer •  Research analyst @petuniaGray
  15. Why aren’t testers doing chaos? @petuniaGray

  16. Before there was Chaos Engineering, there was Chaos Testing @petuniaGray

  17. @petuniaGray Software Development Lifecycle Planning Design Development Testing Maintenance

  18. @petuniaGray It was called chaos testing

  19. @petuniaGray Software Development Lifecycle Planning Design Development Testing Maintenance

  20. The biggest limitation in the fear of delivering software faster

    is the focus on adding more pre-release testing. - Abby Bangser, Platform Test Engineer at MOO @petuniaGray
  21. ...building confidence that we aren’t fragile. - Abby Bangser, Platform

    Test Engineer at MOO @petuniaGray
  22. Testers doing chaos? •  Focused on pre-release testing •  Early

    stages of chaos automation @petuniaGray
  23. Who can start a chaos program? @petuniaGray

  24. Who has? •  Insights @petuniaGray

  25. Who has? •  Insights •  Access @petuniaGray

  26. Who has? •  Insights •  Access •  Buy-in @petuniaGray

  27. Perhaps aggregate bits and pieces from different [resilience engineering] frameworks

    that appeal to you, and then create a practice around it. - Casey Rosenthal, CEO at Verica @petuniaGray
  28. I wish the best of luck to you in that

    undertaking, but I wouldn’t wager that you get it right on your first try. Or your second. - Casey Rosenthal, CEO at Verica @petuniaGray
  29. Infrastructure Talent Goals Maturity Industry So who owns chaos? @petuniaGray

  30. Final lightning thoughts @petuniaGray

  31. More adoption of chaos engineering @petuniaGray

  32. A shift in roles and responsibilities @petuniaGray

  33. Building a culture of resilience @petuniaGray

  34. @petuniaGray Thank you!

  35. Resources •  Building resilient APIs with chaos engineering - Joyce

    Lin •  Chaos people and tools - Chaos Engineering Slack Community •  Introducing Chaos Engineering - Netflix blog 2014 @petuniaGray