From 100 to 1,000+ deployments a day! [Techorama Edition]

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 What does it take to get to the next level?

Slide 4

Slide 4 text

Pat Hermens Currently Development Manager Coding for 15+ years Father & husband Rotterdam

Slide 5

Slide 5 text

5 @phermens

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

Why 1,000+ deployments/day?

Slide 9

Slide 9 text

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

Slide 10

Slide 10 text

10 @phermens “It depends”

Slide 11

Slide 11 text

11 @phermens YAGNI & KISS

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

No content

Slide 19

Slide 19 text

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

Slide 20

Slide 20 text

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

Slide 21

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

Slide 22 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 23

Slide 23 text

No content

Slide 24

Slide 24 text

Prerequisites...

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

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

29 @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 30

Slide 30 text

No content

Slide 31

Slide 31 text

Story time!

Slide 32

Slide 32 text

Responsibility Autonomy Failure Ownership

Slide 33

Slide 33 text

Responsibility Autonomy Failure Ownership

Slide 34

Slide 34 text

Responsibility

Slide 35

Slide 35 text

35 @phermens Hosting & Deployment “DevOps”

Slide 36

Slide 36 text

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

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 A Team D Team F Team B Team C Team E

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 Hosting & Deployment “DevOps” Team H Team A Team D Team G Team E Team J Team F Team B Team I Team C

Slide 44

Slide 44 text

44 @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 45

Slide 45 text

45 @phermens

Slide 46

Slide 46 text

46 @phermens Sorry Kasey!

Slide 47

Slide 47 text

47 @phermens

Slide 48

Slide 48 text

Responsibility Autonomy Failure Ownership

Slide 49

Slide 49 text

Responsibility Autonomy Failure Ownership

Slide 50

Slide 50 text

Autonomy

Slide 51

Slide 51 text

51 @phermens

Slide 52

Slide 52 text

52 @phermens Log4Net + RDP

Slide 53

Slide 53 text

53 @phermens Serilog + Splunk + DataDog

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

No content

Slide 58

Slide 58 text

Responsibility Autonomy Failure Ownership

Slide 59

Slide 59 text

Responsibility Autonomy Failure Ownership

Slide 60

Slide 60 text

60 @phermens Ownership

Slide 61

Slide 61 text

61 @phermens Build System

Slide 62

Slide 62 text

62 @phermens

Slide 63

Slide 63 text

63 @phermens

Slide 64

Slide 64 text

64 @phermens Development team tooling choices

Slide 65

Slide 65 text

65 @phermens Infrastructure team tooling choices

Slide 66

Slide 66 text

66 @phermens

Slide 67

Slide 67 text

67 @phermens What’s next?

Slide 68

Slide 68 text

68 @phermens ? What’s next?

Slide 69

Slide 69 text

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

Slide 70

Slide 70 text

70 @phermens

Slide 71

Slide 71 text

Responsibility Autonomy Failure Ownership

Slide 72

Slide 72 text

Responsibility Autonomy Failure Ownership

Slide 73

Slide 73 text

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

Slide 74

Slide 74 text

74 @phermens Failure

Slide 75

Slide 75 text

75 @phermens

Slide 76

Slide 76 text

No content

Slide 77

Slide 77 text

No content

Slide 78

Slide 78 text

No content

Slide 79

Slide 79 text

No content

Slide 80

Slide 80 text

80 @phermens

Slide 81

Slide 81 text

No content

Slide 82

Slide 82 text

82 @phermens

Slide 83

Slide 83 text

83 @phermens

Slide 84

Slide 84 text

No content

Slide 85

Slide 85 text

85 @phermens #war-room

Slide 86

Slide 86 text

86 @phermens

Slide 87

Slide 87 text

Responsibility Autonomy Failure Ownership

Slide 88

Slide 88 text

Responsibility Autonomy Failure Ownership

Slide 89

Slide 89 text

Questions? If not, drinks follow this talk!

Slide 90

Slide 90 text

Checklists!

Slide 91

Slide 91 text

91 @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 92

Slide 92 text

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