Tweet
Tweet

Slide 1

Slide 1 text

No content

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 Currently Development Manager Coding for 15+ years Father & husband Rotterdam

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

Why 1,000+ deployments/day?

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

8 @phermens “It depends”

Slide 9

Slide 9 text

9 @phermens YAGNI & KISS

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

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

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

Slide 19

Slide 19 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 20

Slide 20 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 21

Slide 21 text

No content

Slide 22

Slide 22 text

Prerequisites...

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

24 @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 25

Slide 25 text

25 @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 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

No content

Slide 29

Slide 29 text

Story time!

Slide 30

Slide 30 text

Responsibility Autonomy Failure Ownership

Slide 31

Slide 31 text

Responsibility Autonomy Failure Ownership

Slide 32

Slide 32 text

Responsibility

Slide 33

Slide 33 text

33 @phermens Hosting & Deployment “DevOps”

Slide 34

Slide 34 text

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

Slide 35

Slide 35 text

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

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 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 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 Team H Team A Team C Team G Team E Team J Team F Team B Team I Team C Team D Team L Team K

Slide 43

Slide 43 text

43 @phermens

Slide 44

Slide 44 text

44 @phermens

Slide 45

Slide 45 text

Responsibility Autonomy Failure Ownership

Slide 46

Slide 46 text

Responsibility Autonomy Failure Ownership

Slide 47

Slide 47 text

Autonomy

Slide 48

Slide 48 text

48 @phermens

Slide 49

Slide 49 text

49 @phermens Log4Net + RDP

Slide 50

Slide 50 text

50 @phermens Serilog + Splunk + DataDog

Slide 51

Slide 51 text

No content

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

Responsibility Autonomy Failure Ownership

Slide 56

Slide 56 text

Responsibility Autonomy Failure Ownership

Slide 57

Slide 57 text

57 @phermens Ownership

Slide 58

Slide 58 text

58 @phermens Build System

Slide 59

Slide 59 text

59 @phermens

Slide 60

Slide 60 text

60 @phermens

Slide 61

Slide 61 text

61 @phermens Development team tooling choices

Slide 62

Slide 62 text

62 @phermens Infrastructure team tooling choices

Slide 63

Slide 63 text

63 @phermens

Slide 64

Slide 64 text

64 @phermens What’s next?

Slide 65

Slide 65 text

65 @phermens ? What’s next?

Slide 66

Slide 66 text

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

Slide 67

Slide 67 text

67 @phermens

Slide 68

Slide 68 text

Responsibility Autonomy Failure Ownership

Slide 69

Slide 69 text

Responsibility Autonomy Failure Ownership

Slide 70

Slide 70 text

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

Slide 71

Slide 71 text

71 @phermens Failure

Slide 72

Slide 72 text

72 @phermens

Slide 73

Slide 73 text

No content

Slide 74

Slide 74 text

No content

Slide 75

Slide 75 text

No content

Slide 76

Slide 76 text

No content

Slide 77

Slide 77 text

77 @phermens

Slide 78

Slide 78 text

No content

Slide 79

Slide 79 text

79 @phermens

Slide 80

Slide 80 text

80 @phermens

Slide 81

Slide 81 text

No content

Slide 82

Slide 82 text

82 @phermens #war-room

Slide 83

Slide 83 text

83 @phermens

Slide 84

Slide 84 text

Responsibility Autonomy Failure Ownership

Slide 85

Slide 85 text

Responsibility Autonomy Failure Ownership

Slide 86

Slide 86 text

Questions? If not, drinks follow this talk!

Slide 87

Slide 87 text

Checklists!

Slide 88

Slide 88 text

88 @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 89

Slide 89 text

89 @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 90

Slide 90 text

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

Slide 91

Slide 91 text

91 @phermens Thanks https://hermens.com.au @phermens