Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Graceful Degradation as a Feature

0 vue

Publié le

Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2nQn2iW.

Lorne Kligerman talks about graceful degradation as an engineering goal which can be confidently tested with Chaos Engineering. By purposely causing failure of one service at a time in a controlled environment, one can safely observe the effect on the end user, whether that’s on a laptop browser, a mobile app, or the result of an API call. Filmed at qconnewyork.com.

Lorne Kligerman currently leads the product team at Gremlin, helping companies avoid outages by running proactive chaos engineering experiments. He last worked at Google Cloud as a Product Manager on App Engine, empowering developers to build applications on a fully managed and resilient platform.

Publié dans : Technologie
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

Graceful Degradation as a Feature

  1. 1. Failing Gracefully As A Feature Lorne Kligerman Director of Product, Gremlin @lklig
  2. 2. InfoQ.com: News & Community Site • 750,000 unique visitors/month • Published in 4 languages (English, Chinese, Japanese and Brazilian Portuguese) • Post content from our QCon conferences • News 15-20 / week • Articles 3-4 / week • Presentations (videos) 12-15 / week • Interviews 2-3 / week • Books 1 / month Watch the video with slide synchronization on InfoQ.com! https://www.infoq.com/presentations/ graceful-degradation-chaos- engineering/
  3. 3. Presented at QCon New York www.qconnewyork.com Purpose of QCon - to empower software development by facilitating the spread of knowledge and innovation Strategy - practitioner-driven conference designed for YOU: influencers of change and innovation in your teams - speakers and topics driving the evolution and innovation - connecting and catalyzing the influencers and innovators Highlights - attended by more than 12,000 delegates since 2007 - held in 9 cities worldwide
  4. 4. 2
  5. 5. 3
  6. 6. 4 Be down in 10! T-Ho 2017 Hey team… bit of a spill but I’m fine.
  7. 7. 5 We Expect Technology To Just Work™
  8. 8. Technical Issues Likely Cost Retailers Billions 12.01.16 Macy’s, Lowe’s hit by Black Friday technical glitches 11.27.17 Retail outages online leave shoppers frustrated on Black Friday 11.23.18 People.com Black Friday Failures @lklig
  9. 9. Wells Fargo accidentally foreclosed hundreds of homeowners 8.7.18 Customers report difficulty accessing Chase Bank mobile and online 2.16.19 Citibank Website down, not working 2.28.19 Investopedia Breaking Banks @lklig
  10. 10. Computer Problems Blamed For Flight Delays 4.1.19 Major US Airlines hit by delays after glitch at vendor 4.1.19 Pilots of doomed Boeing 737 MAX fought the plane’s software and lost 4.4.19 Airline Incidents @lklig
  11. 11. 9 Technology is fragile. When it breaks, we shouldn’t notice. @lklig
  12. 12. 10 Plan ahead to keep your users happy FAILURE GRACEFUL DEGRADATION @lklig
  13. 13. 11 Why Are Failures So Common?
  14. 14. 12 Legacy Systems @lklig
  15. 15. 13 Lack of Testing Failure UI End to end Integration Unit @lklig
  16. 16. 14 With Scale Comes Complexity @lklig
  17. 17. @lklig
  18. 18. @lklig
  19. 19. 17 What Can We Do About It?
  20. 20. 18 Design For Failure
  21. 21. 19@lklig
  22. 22. 20 Designing For Failure Key User Stories & Features Edge Cases From Unexpected User Behaviour Dependency Failures @lklig
  23. 23. 2121@lklig
  24. 24. 22@lklig Loading Screens Are Not Graceful
  25. 25. 23 Inject Failure By Breaking Things On Purpose @lklig
  26. 26. Inject failure one service at a time. Maintain critical functionality. 24@lklig
  27. 27. Common Failures Modes 25 Errors HTTP 400, 401, 402 500, 503 Blackhole Latency @lklig THAT DEGRADE THE USER EXPERIENCE @lklig
  28. 28. 26 Degrade Gracefully
  29. 29. 27 Graceful Degradation ● Provide the best possible experience ● All but the most critical functionality can fall off ● Don’t give up on your users, hold state as long as possible @lklig
  30. 30. 28@lklig When one dependency fails, users are often affected Storage Auth User Data Content Cache Feature 1 Feature 2
  31. 31. 29 Implemented As Designed @lklig
  32. 32. 30 Added Latency @lklig
  33. 33. 31 Blocked Video Link @lklig
  34. 34. 32 Blocked JQuery Request @lklig
  35. 35. 33@lklig
  36. 36. 34 Delight Your Users
  37. 37. 3535 Graceful Degradation Done Right @lklig
  38. 38. 36 Positive Business Impact Product Launch Delight users with new features Success Metrics Quantitative goals of the launch Product Landing Were the goals achieved? Why or why not? What got in way? @lklig
  39. 39. 37@lklig Maintain release velocity Deliver a positive user experience Engineers spend less time in war rooms Plan Experiments Early @lklig
  40. 40. 38 RELIABILITY THROUGH CHAOS ENGINEERING Design for Failure Identify the most critical end user functionality. Inject Failure Impact your system to be sure your user experience isn’t impacted. Degrade Gracefully Plan for non critical functionality not to get in the way. Delight Your Users Your product metrics will show behaviour, no matter the condition. Graceful Degradation As a Feature @lklig
  41. 41. USE LORNE FOR 20% OFF
  42. 42. 40 gremlin.com/lorne
  43. 43. Q&A Lorne Kligerman Director of Product, Gremlin @lklig
  44. 44. Watch the video with slide synchronization on InfoQ.com! https://www.infoq.com/presentations/ graceful-degradation-chaos- engineering/