how devops helps shape
play

HOW DEVOPS HELPS SHAPE SMALL TEAMS AND ARCHITECTURE MATHIAS MEYER, - PowerPoint PPT Presentation

HOW DEVOPS HELPS SHAPE SMALL TEAMS AND ARCHITECTURE MATHIAS MEYER, @ROIDRAGE DEVOPS PRODUCTION AND CULTURE PRODUCTION = ARCHITECTURE ! PRODUCTION = ARCHITECTURE + OPERATIONS(PRODUCTION) P = A + O(P) ARCHITECTURE & OPERATIONS


  1. HOW DEVOPS HELPS SHAPE SMALL TEAMS AND ARCHITECTURE MATHIAS MEYER, @ROIDRAGE

  2. DEVOPS

  3. PRODUCTION AND CULTURE

  4. PRODUCTION = ARCHITECTURE

  5. !

  6. PRODUCTION = ARCHITECTURE + OPERATIONS(PRODUCTION)

  7. P = A + O(P)

  8. ARCHITECTURE & OPERATIONS

  9. MONOLITH

  10. BIG BALL OF MUD

  11. TWO PARTS

  12. WEB FRONTEND

  13. HUB

  14. (WORKER)

  15. HUB'S TODO LIST ▸ Create Builds ▸ Talk to GitHub API ▸ Schedule Builds ▸ Process Build Results ▸ Process Log Updates ▸ Send Build Notifications

  16. HUB BROKE ! A LOT !

  17. SCALE

  18. THE PROFESSIONALIZATION OF TRAVIS CI

  19. METRICS

  20. By a de ing just a few metrics, you get a be tu er idea what you n ef d to track.

  21. MO METRICS, MO PROBLEMS

  22. THE BIG TRAVIS CI OUTAGE OF 2012

  23. PULL REQUESTS

  24. PROBLEMS ▸ Minor changes in the GitHub API ▸ Liberal timeouts ▸ Serial processing ▸ Bug in JRuby

  25. Because failure requires multiple faults, there is no isolated ‘cause’ of an accident. — Richard Cook, How Complex Systems Fail

  26. Each of these faults is nece st ary insu fg icient, only jointly are these causes su fg icient to create an accident. — Richard Cook, How Complex Systems Fail

  27. WHAT DID WE LEARN?

  28. TREAT EXTERNAL APIS LIKE FOES RATHER THAN FRIENDS.

  29. Fail gracefu lm y.

  30. Fail fast.

  31. HOW YOU HANDLE FAILURES IS A BUSINESS DECISION.

  32. Simplify, simplify, simplify. — Henry David Thoreau

  33. Simplify. — Paraphrased

  34. SINGLE RESPONSIBILITIES SEPARATE PROCESSES

  35. INCREASED COMPLEXITY AND INCREASED VELOCITY

  36. A complex system is shaped more by its behaviour in production than its initial design.

  37. COMPLEX ≠ COMPLICATED

  38. THE TRUTH LIES ONLY IN PRODUCTION

  39. ALERTING

  40. BYOC BUILD YOUR OWN COLLECTOR

  41. Every organization ru no ing a software system in production is bound to implement their own monitoring system around it. — Mathias' 1st Law of Monitoring

  42. Every custom monitoring solution is bound to implement cycle checks. — Mathias' 2nd Law of Monitoring

  43. SMALL SERVICES LOOSELY JOINED

  44. SIMPLIFICATION IS THE HALLMARK OF SCALABILITY

  45. MORE COMPONENTS = MORE RESPONSIBILITIES

  46. WHO YOU GONNA CALL?

  47. THE GOAL OF ALERTING ISN'T TO WAKE PEOPLE UP, IT'S TO MAKE SURE THEY CAN SLEEP

  48. Any new alert wi lm wake people up more often than nece st ary initia lm y. — Mathias' 3rd Law of Monitoring:

  49. GIVE ROOM TO IMPROVE

  50. Any organization that designs a system wi lm produce a design whose structure is a copy of the organization's co mn unication structure. — Conways' Law

  51. BIG TEAMS = BIG SYSTEMS?

  52. DISTRIBUTED TEAMS = DISTRIBUTED SYSTEMS?

  53. ASYNCHRONOUS COMMUNICATION = ASYNCHRONOUS SYSTEMS?

  54. FLEXIBILITY + ADAPTABILITY

  55. CONTINUOUS IMPROVEMENT

  56. EVERYONE'S ON CALL

  57. Any alert that tri gh ers more than once a w ef k wi lm become part of normal procedure. — Mathias' 4th Law of Monitoring

  58. MONITORING IS A PROCESS NOT A FEATURE

  59. OUR ALERTING IS FAR FROM IDEAL

  60. LEARN FROM UNEXPECTED EVENTS

  61. ANDON CORD

  62. BLAMELESS POSTMORTEMS

  63. DEVOPS?

  64. PRODUCTION IS A SHARED RESPONSIBILITY

  65. You build it, you run it. — Werner Vogels

  66. FOCUS ON CONTINUOUS LEARNING

  67. DEVOPS DIDN'T SHAPE OUR TEAM

  68. OUR TEAM EVOLVED INTO SOMETHING THAT LOOKS LIKE DEVOPS

  69. mathias@travis-ci.com

Recommend


More recommend