Slide 1
Slide 1 text
No content
Slide 2
Slide 2 text
From 100 to 1,000+ deployments a day
Pat Hermens
@phermens
Slide 3
Slide 3 text
From 100 to 1,000+
deployments a day
Pat Hermens
@phermens
Slide 4
Slide 4 text
Pat Hermens
Development Manager
Coding for 15+ years
Father & husband
Rotterdam
Slide 5
Slide 5 text
No content
Slide 6
Slide 6 text
No content
Slide 7
Slide 7 text
Why 1,000+ deployments/day?
Slide 8
Slide 8 text
8
@phermens
¯\_(ツ)_/¯
Slide 9
Slide 9 text
9
@phermens
“It depends”
Slide 10
Slide 10 text
10
@phermens
YAGNI
& KISS
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
No content
Slide 16
Slide 16 text
No content
Slide 17
Slide 17 text
No content
Slide 18
Slide 18 text
100 / 1,000 / 10,000; so what?
Slide 19
Slide 19 text
http://www.cs.utexas.edu/users/ewd/ewd02xx/ewd249.pdf
Slide 20
Slide 20 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!
...
Slide 21
Slide 21 text
... A one-year old child will crawl on all fours with a speed of,
say, one mile per hour. But a speed of a thousand miles per
hour is that of a supersonic jet.
Considered as objects with moving ability the child and the jet
are incomparable, for whatever one can do the other cannot
and vice versa.
— Edsger Dijkstra, 1969
Slide 22
Slide 22 text
No content
Slide 23
Slide 23 text
Prerequisites...
Slide 24
Slide 24 text
No content
Slide 25
Slide 25 text
25
@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 26
Slide 26 text
26
@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 27
Slide 27 text
27
@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 28
Slide 28 text
28
@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 29
Slide 29 text
No content
Slide 30
Slide 30 text
Story time!
Slide 31
Slide 31 text
Responsibility Autonomy
Failure
Ownership
Slide 32
Slide 32 text
Responsibility Autonomy
Failure
Ownership
Slide 33
Slide 33 text
Responsibility
Slide 34
Slide 34 text
34
@phermens
Hosting &
Deployment
“DevOps”
Slide 35
Slide 35 text
35
@phermens
Hosting &
Deployment
“DevOps”
Team
A
Team
D
Team
B
Team
C
Slide 36
Slide 36 text
36
@phermens
Hosting &
Deployment
“DevOps”
Team
A
Team
D
Team
F
Team
B
Team
C
Team
E
Slide 37
Slide 37 text
37
@phermens
Hosting &
Deployment
“DevOps”
Team
A
Team
D
Team
F
Team
B
Team
C
Team
E
Slide 38
Slide 38 text
38
@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 39
Slide 39 text
39
@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 40
Slide 40 text
40
@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 41
Slide 41 text
41
@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 42
Slide 42 text
42
@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 43
Slide 43 text
43
@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
Hosting
&
Deploy-
ment
Slide 44
Slide 44 text
44
@phermens
Slide 45
Slide 45 text
45
@phermens
Slide 46
Slide 46 text
46
@phermens
Slide 47
Slide 47 text
Responsibility Autonomy
Failure
Ownership
Slide 48
Slide 48 text
Responsibility Autonomy
Failure
Ownership
Slide 49
Slide 49 text
Autonomy
Slide 50
Slide 50 text
Autonomy
Slide 51
Slide 51 text
51
@phermens
Serilog + Splunk + DataDog
Slide 52
Slide 52 text
No content
Slide 53
Slide 53 text
No content
Slide 54
Slide 54 text
No content
Slide 55
Slide 55 text
No content
Slide 56
Slide 56 text
No content
Slide 57
Slide 57 text
Autonomy
Slide 58
Slide 58 text
No content
Slide 59
Slide 59 text
59
@phermens
Slide 60
Slide 60 text
60
@phermens
Slide 61
Slide 61 text
61
@phermens
Slide 62
Slide 62 text
62
@phermens
$ $ $
$ $
Slide 63
Slide 63 text
63
@phermens
$ $ $
$ $
Slide 64
Slide 64 text
64
@phermens
Slide 65
Slide 65 text
65
@phermens
UDP
Slide 66
Slide 66 text
66
@phermens
UDP
Slide 67
Slide 67 text
67
@phermens
UDP
Slide 68
Slide 68 text
68
@phermens
UDP
Slide 69
Slide 69 text
69
@phermens
UDP
Slide 70
Slide 70 text
70
@phermens
Slide 71
Slide 71 text
71
@phermens
TCP
Slide 72
Slide 72 text
72
@phermens
TCP
Slide 73
Slide 73 text
73
@phermens
Slide 74
Slide 74 text
74
@phermens
Slide 75
Slide 75 text
75
@phermens
API Gateway Lambda CloudWatch
Slide 76
Slide 76 text
76
@phermens
API Gateway Kinesis Lambda CloudWatch
Slide 77
Slide 77 text
77
@phermens
AWS Lambda stats for Vanessa Optima Prime (as of 2018-09-28)
Last 30 days
Last 7 days
Slide 78
Slide 78 text
78
@phermens
AWS Lambda stats for Vanessa Optima Prime (as of 2018-09-28)
Last 30 days
Last 7 days
Slide 79
Slide 79 text
79
@phermens
Slide 80
Slide 80 text
80
@phermens
Slide 81
Slide 81 text
Responsibility Autonomy
Failure
Ownership
Slide 82
Slide 82 text
Responsibility Autonomy
Failure
Ownership
Slide 83
Slide 83 text
83
@phermens
Ownership
Slide 84
Slide 84 text
84
@phermens
Build System
Slide 85
Slide 85 text
85
@phermens
Slide 86
Slide 86 text
86
@phermens
Slide 87
Slide 87 text
87
@phermens
Development team tooling choices
Slide 88
Slide 88 text
88
@phermens
Infrastructure team tooling choices
Slide 89
Slide 89 text
89
@phermens
Slide 90
Slide 90 text
90
@phermens
What’s next?
Slide 91
Slide 91 text
91
@phermens
What’s next?
?
Slide 92
Slide 92 text
92
@phermens
¯\_(ツ)_/¯
Slide 93
Slide 93 text
93
@phermens
Slide 94
Slide 94 text
Responsibility Autonomy
Failure
Ownership
Slide 95
Slide 95 text
Responsibility Autonomy
Failure
Ownership
Slide 96
Slide 96 text
96
@phermens
Fail early, fail often,
but always fail forward.
Slide 97
Slide 97 text
97
@phermens
Failure
Slide 98
Slide 98 text
98
@phermens
Slide 99
Slide 99 text
99
@phermens
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
104
@phermens
Slide 105
Slide 105 text
No content
Slide 106
Slide 106 text
NOTE:
20 cubic
centimeters
Slide 107
Slide 107 text
No content
Slide 108
Slide 108 text
NOTE:
Now 50cc!
Slide 109
Slide 109 text
No content
Slide 110
Slide 110 text
NOTE:
49 cubic
centimeters
Slide 111
Slide 111 text
No content
Slide 112
Slide 112 text
No content
Slide 113
Slide 113 text
NOTE:
More than
49cc’s!
Slide 114
Slide 114 text
No content
Slide 115
Slide 115 text
No content
Slide 116
Slide 116 text
No content
Slide 117
Slide 117 text
No content
Slide 118
Slide 118 text
NOTE:
Now 45cc!
Slide 119
Slide 119 text
No content
Slide 120
Slide 120 text
No content
Slide 121
Slide 121 text
121
@phermens
Slide 122
Slide 122 text
122
@phermens
Slide 123
Slide 123 text
No content
Slide 124
Slide 124 text
124
@phermens
#war-room
Slide 125
Slide 125 text
125
@phermens
Slide 126
Slide 126 text
Responsibility Autonomy
Failure
Ownership
Slide 127
Slide 127 text
Responsibility Autonomy
Failure
Ownership
Slide 128
Slide 128 text
128
@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 129
Slide 129 text
Questions?
Slide 130
Slide 130 text
Checklists!
Slide 131
Slide 131 text
131
@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 132
Slide 132 text
132
@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 133
Slide 133 text
https://sddconf.com/brands/sdd/library/DOLLARD-Debugging.pdf
Slide 134
Slide 134 text
134
@phermens
Thanks
https://hermens.com.au
@phermens