From 100 to 1000+ deployments a day [CodeMotion Edition]

Slide 1

Slide 1 text

From 100 to 1000+ deployments a day Pat Hermens Amsterdam | April 2-3, 2019

Slide 2

Slide 2 text

From 100 to 1,000+ deployments What does it take to get to the next level?

Slide 3

Slide 3 text

Pat Hermens Development Manager Coding for 15+ years Father & husband Rotterdam, Netherlands @phermens [email protected]

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

Why 1,000+ deployments/day?

Slide 6

Slide 6 text

6 @phermens ¯\_(ツ)_/¯

Slide 7

Slide 7 text

7 @phermens “It depends”

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

100 / 1,000 / 10,000; so what?

Slide 16

Slide 16 text

http://www.cs.utexas.edu/users/ewd/ewd02xx/ewd249.pdf

Slide 17

Slide 17 text

… Apparently we are too much trained to disregard differences in scale, to treat them as “gradual differences that are not essential.” We tell ourselves that what we can do once, we can also do twice and by induction, we fool ourselves into believing that we can do it as many times as needed, but this is just not true! — Edsger Dijkstra, 1969

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

Prerequisites...

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

21 @phermens The “faster to master” checklist Developing ⬜ Coding guidelines ⬜ Code reviews ⬜ Code analysis ⬜ Short-lived branches ⬜ Feature toggles Monitoring ⬜ Defined key metrics ⬜ Measure – create dashboards ⬜ Proactivity – add alerting (& act!) Testing ⬜ Unit tests ⬜ Module tests ⬜ Integration tests ⬜ End-to-end tests ⬜ Test automation Deploying ⬜ Continuous Integration ⬜ Continuous Delivery ⬜ Infrastructure as Code

Slide 22

Slide 22 text

22 @phermens Developing ☑ Coding guidelines ☑ Code reviews ⬜ Code analysis ☑ Short-lived branches ⬜ Feature toggles Monitoring ☑ Defined key metrics ⬜ Measure – create dashboards ⬜ Proactivity – add alerting (& act!) Testing ☑ Unit tests ⬜ Module tests ⬜ Integration tests ⬜ End-to-end tests ☑ Test automation Deploying ☑ Continuous Integration ⬜ Continuous Delivery ⬜ Infrastructure as Code The “faster to master” checklist

Slide 23

Slide 23 text

23 @phermens Developing ☑ Coding guidelines ☑ Code reviews ⬜ Code analysis ☑ Short-lived branches ☑ Feature toggles Monitoring ☑ Defined key metrics ☑ Measure – create dashboards ⬜ Proactivity – add alerting (& act!) Testing ☑ Unit tests ☑ Module tests ⬜ Integration tests ☑ End-to-end tests ☑ Test automation Deploying ☑ Continuous Integration ☑ Continuous Delivery ⬜ Infrastructure as Code The “faster to master” checklist

Slide 24

Slide 24 text

24 @phermens Developing ☑ Coding guidelines ☑ Code reviews ☑ Code analysis ☑ Short-lived branches ☑ Feature toggles Monitoring ☑ Defined key metrics ☑ Measure – create dashboards ☑ Proactivity – add alerting (& act!) Testing ☑ Unit tests ☑ Module tests ☑ Integration tests ☑ End-to-end tests ☑ Test automation Deploying ☑ Continuous Integration ☑ Continuous Delivery ☑ Infrastructure as Code The “faster to master” checklist

Slide 25

Slide 25 text

Story time!

Slide 26

Slide 26 text

Responsibility Autonomy Failure Ownership

Slide 27

Slide 27 text

Responsibility Autonomy Failure Ownership

Slide 28

Slide 28 text

Responsibility

Slide 29

Slide 29 text

29 @phermens Hosting & Deployment “DevOps”

Slide 30

Slide 30 text

30 @phermens Hosting & Deployment “DevOps” Team A Team D Team B Team C

Slide 31

Slide 31 text

31 @phermens Hosting & Deployment “DevOps” Team A Team D Team F Team B Team C Team E

Slide 32

Slide 32 text

32 @phermens Hosting & Deployment “DevOps” Team A Team D Team F Team B Team C Team E

Slide 33

Slide 33 text

33 @phermens Hosting & Deployment “DevOps” Team H Team A Team D Team G Team E Team J Team F Team B Team I Team C

Slide 34

Slide 34 text

34 @phermens Hosting & Deployment “DevOps” Team H Team A Team D Team G Team E Team J Team F Team B Team I Team C

Slide 35

Slide 35 text

35 @phermens Hosting & Deployment “DevOps” Team H Team A Team D Team G Team E Team J Team F Team B Team I Team C

Slide 36

Slide 36 text

36 @phermens Hosting & Deployment “DevOps” Team H Team A Team D Team G Team E Team J Team F Team B Team I Team C

Slide 37

Slide 37 text

37 @phermens Hosting & Deployment “DevOps” Team H Team A Team D Team G Team E Team J Team F Team B Team I Team C

Slide 38

Slide 38 text

38 @phermens Team H Team A Team C Team G Team E Team J Team F Team B Team I Team C Team D Team L Deploy- ment

Slide 39

Slide 39 text

39 @phermens

Slide 40

Slide 40 text

Responsibility Autonomy Failure Ownership

Slide 41

Slide 41 text

Responsibility Autonomy Failure Ownership

Slide 42

Slide 42 text

Autonomy

Slide 43

Slide 43 text

Autonomy

Slide 44

Slide 44 text

44 @phermens Serilog + Splunk + DataDog

Slide 45

Slide 45 text

No content

Slide 46

Slide 46 text

No content

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

Autonomy

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

52 @phermens

Slide 53

Slide 53 text

53 @phermens

Slide 54

Slide 54 text

54 @phermens

Slide 55

Slide 55 text

55 @phermens

Slide 56

Slide 56 text

56 @phermens

Slide 57

Slide 57 text

57 @phermens

Slide 58

Slide 58 text

58 @phermens UDP

Slide 59

Slide 59 text

59 @phermens UDP

Slide 60

Slide 60 text

60 @phermens UDP

Slide 61

Slide 61 text

61 @phermens UDP

Slide 62

Slide 62 text

62 @phermens UDP

Slide 63

Slide 63 text

63 @phermens

Slide 64

Slide 64 text

64 @phermens TCP

Slide 65

Slide 65 text

65 @phermens TCP

Slide 66

Slide 66 text

66 @phermens

Slide 67

Slide 67 text

67 @phermens

Slide 68

Slide 68 text

68 @phermens

Slide 69

Slide 69 text

69 @phermens Hosting & Deployment “DevOps” Team H Team A Team D Team G Team E Team J Team F Team B Team I Team C

Slide 70

Slide 70 text

70 @phermens

Slide 71

Slide 71 text

71 @phermens

Slide 72

Slide 72 text

72 @phermens

Slide 73

Slide 73 text

73 @phermens

Slide 74

Slide 74 text

74 @phermens

Slide 75

Slide 75 text

Responsibility Autonomy Failure Ownership

Slide 76

Slide 76 text

Responsibility Autonomy Failure Ownership

Slide 77

Slide 77 text

77 @phermens Ownership

Slide 78

Slide 78 text

78 @phermens Build System

Slide 79

Slide 79 text

79 @phermens

Slide 80

Slide 80 text

80 @phermens

Slide 81

Slide 81 text

81 @phermens Development team tooling choices

Slide 82

Slide 82 text

82 @phermens Infrastructure team tooling choices

Slide 83

Slide 83 text

83 @phermens

Slide 84

Slide 84 text

84 @phermens What’s next?

Slide 85

Slide 85 text

85 @phermens ? What’s next?

Slide 86

Slide 86 text

86 @phermens ¯\_(ツ)_/¯

Slide 87

Slide 87 text

87 @phermens

Slide 88

Slide 88 text

Responsibility Autonomy Failure Ownership

Slide 89

Slide 89 text

Responsibility Autonomy Failure Ownership

Slide 90

Slide 90 text

90 @phermens Fail early, fail often, but always fail forward.

Slide 91

Slide 91 text

91 @phermens Failure

Slide 92

Slide 92 text

No content

Slide 93

Slide 93 text

No content

Slide 94

Slide 94 text

No content

Slide 95

Slide 95 text

No content

Slide 96

Slide 96 text

No content

Slide 97

Slide 97 text

No content

Slide 98

Slide 98 text

98 @phermens [REDACTED] [REDACTED]

Slide 99

Slide 99 text

No content

Slide 100

Slide 100 text

No content

Slide 101

Slide 101 text

No content

Slide 102

Slide 102 text

No content

Slide 103

Slide 103 text

No content

Slide 104

Slide 104 text

No content

Slide 105

Slide 105 text

No content

Slide 106

Slide 106 text

No content

Slide 107

Slide 107 text

No content

Slide 108

Slide 108 text

No content

Slide 109

Slide 109 text

No content

Slide 110

Slide 110 text

No content

Slide 111

Slide 111 text

No content

Slide 112

Slide 112 text

No content

Slide 113

Slide 113 text

No content

Slide 114

Slide 114 text

No content

Slide 115

Slide 115 text

115 @phermens

Slide 116

Slide 116 text

116 @phermens

Slide 117

Slide 117 text

No content

Slide 118

Slide 118 text

118 @phermens #war-room

Slide 119

Slide 119 text

Responsibility Autonomy Failure Ownership

Slide 120

Slide 120 text

Responsibility Autonomy Failure Ownership

Slide 121

Slide 121 text

121 @phermens The “faster to master” checklist Developing ⬜ Coding guidelines ⬜ Code reviews ⬜ Code analysis ⬜ Short-lived branches ⬜ Feature toggles Monitoring ⬜ Defined key metrics ⬜ Measure – create dashboards ⬜ Proactivity – add alerting (& act!) Testing ⬜ Unit tests ⬜ Module tests ⬜ Integration tests ⬜ End-to-end tests ⬜ Test automation Deploying ⬜ Continuous Integration ⬜ Continuous Delivery ⬜ Infrastructure as Code

Slide 122

Slide 122 text

122 @phermens The “100 to 1,000” checklist Responsibility ⬜ Can I control my deployments? ⬜ Have I removed all bottlenecks? ⬜ Do I have good support systems? ⬜ Am I collaborating with my peers? Autonomy ⬜ Freedom to innovate/improve? ⬜ Am I in control and independent? ⬜ Can I find out what went wrong? ⬜ Do I have the skills to fix it? Ownership ⬜ Agreed interfaces (or contracts?) ⬜ Out-of-the-box solutions? ⬜ Tooling is 100% automated? ⬜ Local build == “Production” build? Failure ⬜ Monitoring = Alerting = Action ⬜ Take pride in improving ⬜ Small deliverables, quickly ⬜ Non-blocking deployments

Slide 123

Slide 123 text

Questions?

Slide 124

Slide 124 text

Checklists!

Slide 125

Slide 125 text

125 @phermens The “faster to master” checklist Developing ⬜ Coding guidelines ⬜ Code reviews ⬜ Code analysis ⬜ Short-lived branches ⬜ Feature toggles Monitoring ⬜ Defined key metrics ⬜ Measure – create dashboards ⬜ Proactivity – add alerting (& act!) Testing ⬜ Unit tests ⬜ Module tests ⬜ Integration tests ⬜ End-to-end tests ⬜ Test automation Deploying ⬜ Continuous Integration ⬜ Continuous Delivery ⬜ Infrastructure as Code

Slide 126

Slide 126 text

126 @phermens The “100 to 1,000” checklist Responsibility ⬜ Can I control my deployments? ⬜ Have I removed all bottlenecks? ⬜ Do I have good support systems? ⬜ Am I collaborating with my peers? Autonomy ⬜ Freedom to innovate/improve? ⬜ Am I in control and independent? ⬜ Can I find out what went wrong? ⬜ Do I have the skills to fix it? Ownership ⬜ Agreed interfaces or contracts? ⬜ Out-of-the-box solutions? ⬜ Tooling is 100% automated? ⬜ Local build == “Production” build? Failure ⬜ Monitoring = Alerting = Action ⬜ Take pride in improving ⬜ Small deliverables, quickly ⬜ Non-blocking deployments

Slide 127

Slide 127 text

https://sddconf.com/brands/sdd/library/DOLLARD-Debugging.pdf

Slide 128

Slide 128 text

128 @phermens Thanks! @phermens hermens.com.au [email protected] careersatcoolblue.com