Nine Ways To Fail at Cloud Native (keynote)

A presentation at Sphere.IT in October 2019 in Warsaw, Poland by Holly Cummins

Slide 1

Slide 1

Nine Ways To Fail At Cloud Native Holly Cummins IBM Garage @holly_cummins

Slide 2

Slide 2

An expert is a person who has found out by their own painful experience all the mistakes that one can make in a very narrow field. — Niels Bohr IBM Garage @holly_cummins

Slide 3

Slide 3

I’m a consultant with the IBM Garage. These are my scary stories #IBMGarage @holly_cummins

Slide 4

Slide 4

fail 1 the magic morphing meaning

Slide 5

Slide 5

so, what is cloud native? #IBMGarage @holly_cummins

Slide 6

Slide 6

IBM Garage @holly_cummins

Slide 7

Slide 7

born on the cloud IBM Garage @holly_cummins

Slide 8

Slide 8

born on the cloud IBM Garage @holly_cummins

Slide 9

Slide 9

microservices born on the cloud IBM Garage @holly_cummins

Slide 10

Slide 10

born on the cloud IBM Garage microservices @holly_cummins

Slide 11

Slide 11

kubernetes born on the cloud IBM Garage microservices @holly_cummins

Slide 12

Slide 12

born on the cloud IBM Garage microservices kubernetes @holly_cummins

Slide 13

Slide 13

devops born on the cloud IBM Garage microservices kubernetes @holly_cummins

Slide 14

Slide 14

born on the cloud IBM Garage microservices kubernetes devops @holly_cummins

Slide 15

Slide 15

born on the cloud IBM Garage microservices kubernetes devops modern and nice @holly_cummins

Slide 16

Slide 16

born on the cloud microservices kubernetes devops modern and nice IBM Garage @holly_cummins

Slide 17

Slide 17

synonym for ‘cloud’ born on the cloud microservices kubernetes devops modern and nice IBM Garage @holly_cummins

Slide 18

Slide 18

born on the cloud microservices kubernetes devops synonym for ‘cloud’ modern and nice IBM Garage @holly_cummins

Slide 19

Slide 19

?? IBM Garage ?? ?? ?? idempotent ?? ?? @holly_cummins

Slide 20

Slide 20

rerunnable IBM Garage @holly_cummins

Slide 21

Slide 21

born on the cloud kubernetes microservices IBM Garage devops buzzword for ‘cloud’ modern and nice rerunnable @holly_cummins

Slide 22

Slide 22

why are there no microservices in this cloud native app Alice? #IBMGarage @holly_cummins

Slide 23

Slide 23

fail 2 the muddy goal

Slide 24

Slide 24

why cloud? © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 25

Slide 25

cost © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 26

Slide 26

cost el a s t i c i t y © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 27

Slide 27

s cost pee d © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 28

Slide 28

exotic capabilities © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 29

Slide 29

security @holly_cummins

Slide 30

Slide 30

why is the cloud only saving us money, Alice? #IBMGarage @holly_cummins

Slide 31

Slide 31

fail 3 the not-actually-continuous continuous integration and continuous deployment

Slide 32

Slide 32

“we have a CI/CD” #IBMGarage @holly_cummins

Slide 33

Slide 33

CI/CD is something you do not a tool you buy #IBMGarage @holly_cummins

Slide 34

Slide 34

“i’ll merge my branch into our CI next week” #IBMGarage @holly_cummins

Slide 35

Slide 35

“CI/CD … CI/CD … CI/CD … we release every six months … CI/CD …. ” #IBMGarage @holly_cummins

Slide 36

Slide 36

continuous. I don’t think that word means what you think it means. #IBMGarage @holly_cummins

Slide 37

Slide 37

how often should you push to master? #IBMGarage @holly_cummins

Slide 38

Slide 38

how often should you push to master? integrate? #IBMGarage @holly_cummins

Slide 39

Slide 39

how often should you push to master? integrate? every character #IBMGarage @holly_cummins

Slide 40

Slide 40

how often should you push to master? integrate? every character actually continuous … but stupid #IBMGarage @holly_cummins

Slide 41

Slide 41

how often should you push to master? integrate? every character every commit (several times an hour) actually continuous … but stupid #IBMGarage @holly_cummins

Slide 42

Slide 42

how often should you push to master? integrate? every character every commit (several times an hour) every few commits (several times a day) actually continuous … but stupid #IBMGarage @holly_cummins

Slide 43

Slide 43

how often should you push to master? integrate? every character every commit (several times an hour) every few commits (several times a day) once a day actually continuous … but stupid #IBMGarage @holly_cummins

Slide 44

Slide 44

how often should you push to master? integrate? every character every commit (several times an hour) every few commits (several times a day) once a day once a week actually continuous … but stupid #IBMGarage @holly_cummins

Slide 45

Slide 45

how often should you push to master? integrate? every character every commit (several times an hour) every few commits (several times a day) once a day once a week once a month actually continuous … but stupid #IBMGarage @holly_cummins

Slide 46

Slide 46

how often should you push to master? integrate? every character every commit (several times an hour) every few commits (several times a day) once a day once a week once a month once every six months actually continuous … but stupid #IBMGarage @holly_cummins

Slide 47

Slide 47

how often should you push to master? integrate? every character every commit (several times an hour) every few commits (several times a day) once a day once a week once a month once every six months actually continuous … but stupid #IBMGarage trunk-based development @holly_cummins

Slide 48

Slide 48

how often should you push to master? integrate? every character every commit (several times an hour) every few commits (several times a day) once a day ok actually continuous … but stupid #IBMGarage once a week once a month once every six months trunk-based development @holly_cummins

Slide 49

Slide 49

how often should you push to master? integrate? every character every commit (several times an hour) every few commits (several times a day) once a day ok actually continuous … but stupid #IBMGarage bad once a week once a month once every six months trunk-based development @holly_cummins

Slide 50

Slide 50

how often should you push to master? integrate? every character every commit (several times an hour) every few commits (several times a day) once a day ok once a week once a month once every six months bad bad actually continuous … but stupid #IBMGarage trunk-based development @holly_cummins

Slide 51

Slide 51

how often should you push to master? integrate? every character every commit (several times an hour) every few commits (several times a day) once a day ok once a week once a month once every six months bad bad seriously? actually continuous … but stupid #IBMGarage trunk-based development @holly_cummins

Slide 52

Slide 52

how often should you push to master? integrate? every character every commit (several times an hour) every few commits (several times a day) once a day ok once a week once a month once every six months bad bad my favourite actually continuous … but stupid #IBMGarage seriously? trunk-based development @holly_cummins

Slide 53

Slide 53

how often should you release? every push (many times a day) every user story every epic once a sprint once a quarter #IBMGarage once every two years @holly_cummins

Slide 54

Slide 54

deploy? how often should you release? every push (many times a day) every user story every epic once a sprint once a quarter #IBMGarage once every two years @holly_cummins

Slide 55

Slide 55

deploy? how often should you release? every push (many times a day) every user story every epic once a sprint once a quarter once every two years (need a good handle on feature flags) #IBMGarage @holly_cummins

Slide 56

Slide 56

deploy? how often should you release? every push (many times a day) every user story every epic once a sprint once a quarter ok once every two years (need a good handle on feature flags) #IBMGarage @holly_cummins

Slide 57

Slide 57

deploy? how often should you release? every push (many times a day) every user story every epic once a sprint once a quarter ok (need a good handle on feature flags) #IBMGarage once every two years oldschool @holly_cummins

Slide 58

Slide 58

deploy? how often should you release? every push (many times a day) every user story every epic once a sprint once a quarter ok once every two years sigh (need a good handle on feature flags) #IBMGarage oldschool @holly_cummins

Slide 59

Slide 59

deploy? how often should you release? every push (many times a day) every user story every epic once a sprint once a quarter ok ok once every two years sigh (need a good handle on feature flags) #IBMGarage oldschool @holly_cummins

Slide 60

Slide 60

deploy? how often should you release? every push (many times a day) every user story every epic once a sprint once a quarter ok ok once every two years sigh hardcore (need a good handle on feature flags) #IBMGarage oldschool @holly_cummins

Slide 61

Slide 61

deploy? how often should you release? every push (many times a day) every user story every epic once a sprint once a quarter ok ok once every two years sigh hardcore (need a good handle on feature flags) #IBMGarage my favourite oldschool @holly_cummins

Slide 62

Slide 62

how often should you test in staging? #IBMGarage @holly_cummins

Slide 63

Slide 63

how often should you test in staging? deliver? #IBMGarage @holly_cummins

Slide 64

Slide 64

how often should you test in staging? deliver? every push my favourite #IBMGarage @holly_cummins

Slide 65

Slide 65

“we can’t actually release this.” #IBMGarage @holly_cummins

Slide 66

Slide 66

why? #IBMGarage @holly_cummins

Slide 67

Slide 67

what’s stopping more frequent deploys? #IBMGarage @holly_cummins

Slide 68

Slide 68

“we can’t release this microservice… we deploy all our microservices at the same time.” #IBMGarage @holly_cummins

Slide 69

Slide 69

“we can’t ship until every feature is complete” © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 70

Slide 70

if you’re not embarrassed by your first release it was too late - Reid Hoffman #IBMGarage @holly_cummins

Slide 71

Slide 71

what’s the point of architecture that can go faster, if you don’t go faster? © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 72

Slide 72

how not to drive a car © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 73

Slide 73

feedback is good engineering © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 74

Slide 74

feedback is good business © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 75

Slide 75

deferred wiring #IBMGarage @holly_cummins

Slide 76

Slide 76

feature flags #IBMGarage @holly_cummins

Slide 77

Slide 77

A/B testing canary deploys #IBMGarage @holly_cummins

Slide 78

Slide 78

fail 4 the lockeddown totally rigid inflexible un-cloudy cloud

Slide 79

Slide 79

“we’ve scheduled the architecture board review for a month after the project is ready to ship” © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 80

Slide 80

“this provisioning software is broken” #IBMGarage @holly_cummins

Slide 81

Slide 81

10 minute provision-time what we sold “this provisioning software is broken” #IBMGarage @holly_cummins

Slide 82

Slide 82

what the client thought they’d got 10 minute provision-time what we sold 3 month provisiontime “this provisioning software is broken” #IBMGarage @holly_cummins

Slide 83

Slide 83

what the client thought they’d got 10 minute provision-time the reason 3 month provisiontime 84-step pre-approval process what we sold “this provisioning software is broken” #IBMGarage @holly_cummins

Slide 84

Slide 84

#IBMGarage @holly_cummins

Slide 85

Slide 85

#IBMGarage @holly_cummins

Slide 86

Slide 86

old-style governance isn’t going to work #IBMGarage @holly_cummins

Slide 87

Slide 87

Provider A #IBMGarage @holly_cummins

Slide 88

Slide 88

Provider A Provider B “we’re going to change cloud provider to fix our procurement process!” #IBMGarage @holly_cummins

Slide 89

Slide 89

Provider A Provider B “we’re going to change cloud provider to fix our procurement process!” #IBMGarage @holly_cummins

Slide 90

Slide 90

if the developers are the only ones changing, cloud native is not going to work #IBMGarage @holly_cummins

Slide 91

Slide 91

fail 5 the mystery money pit

Slide 92

Slide 92

the cloud makes it so easy to provision hardware. IBM Garage @holly_cummins

Slide 93

Slide 93

that doesn’t mean the hardware is free. IBM Garage @holly_cummins

Slide 94

Slide 94

or useful. IBM Garage @holly_cummins

Slide 95

Slide 95

Hey boss, I created a Kubernetes cluster. IBM Garage @holly_cummins

Slide 96

Slide 96

Hey boss, I created a Kubernetes cluster. I forgot it for 2 months. IBM Garage @holly_cummins

Slide 97

Slide 97

Hey boss, I created a Kubernetes cluster. I forgot it for 2 months. … and it’s £1000 a month. IBM Garage @holly_cummins

Slide 98

Slide 98

Slide 99

Slide 99

Slide 100

Slide 100

There is surely nothing quite so useless as doing with great efficiency what should not be done at all. — Peter Drucker IBM Garage @holly_cummins

Slide 101

Slide 101

ouch IBM Garage @holly_cummins

Slide 102

Slide 102

“we have no idea how much we’re spending on cloud.” IBM Garage @holly_cummins

Slide 103

Slide 103

cloud to manage your clouds IBM Garage @holly_cummins

Slide 104

Slide 104

IBM Garage @holly_cummins

Slide 105

Slide 105

fail 6 cloud-native spaghetti

Slide 106

Slide 106

“every time we change one microservice, another breaks” #IBMGarage @holly_cummins

Slide 107

Slide 107

distributed != decoupled © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 108

Slide 108

“each of our microservices has duplicated the same object model … with twenty classes and seventy fields” © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 109

Slide 109

Microservice © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 110

Slide 110

Microservice Domain © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 111

Slide 111

Microservice Domain © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 112

Slide 112

© 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 113

Slide 113

Courtesy NASA/ JPL-Caltech © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 114

Slide 114

© 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 115

Slide 115

© 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 116

Slide 116

Slide 117

Slide 117

metric units

Slide 118

Slide 118

metric units imperial units

Slide 119

Slide 119

metric units imperial units distributing did not help

Slide 120

Slide 120

microservices need consumer-driven contract tests © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 121

Slide 121

fail 7 the ‘someday’ automation

Slide 122

Slide 122

“our tests aren’t automated” © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 123

Slide 123

“we don’t know if our code works” © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 124

Slide 124

“we don’t know if our code works” © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 125

Slide 125

systems will behave in unexpected ways © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 126

Slide 126

dependency updates can change behaviour © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 127

Slide 127

“we can’t ship until we have more confidence in the quality” © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 128

Slide 128

microservices need automated integration tests © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 129

Slide 129

not a good CI/CD indicator a good CI/CD indicator “we don’t know when the build is broken” © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 130

Slide 130

a good build radiator © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 131

Slide 131

© 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 132

Slide 132

“oh yes, that build has been broken for a few weeks…” © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 133

Slide 133

fail 8 microservices ops mayhem

Slide 134

Slide 134

@holly_cummins

Slide 135

Slide 135

security @holly_cummins

Slide 136

Slide 136

app Built artefact boundary middleware OS virtualisation hardware @holly_cummins

Slide 137

Slide 137

app app middleware middleware OS OS virtualisation hardware Built artefact boundary virtualisation hardware @holly_cummins

Slide 138

Slide 138

app app middleware middleware OS OS virtualisation hardware Built artefact boundary virtualisation hardware @holly_cummins

Slide 139

Slide 139

Developers are responsible for security in the cloud. @holly_cummins

Slide 140

Slide 140

build security in everywhere

Slide 141

Slide 141

@holly_cummins

Slide 142

Slide 142

make releases deeply boring @holly_cummins

Slide 143

Slide 143

how to brick a spaceprobe Phobos 1 © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 144

Slide 144

“we couldn’t get the automated checks to work, so we bypassed them” © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 145

Slide 145

SRE #IBMGarage @holly_cummins

Slide 146

Slide 146

site reliability engineering #IBMGarage @holly_cummins

Slide 147

Slide 147

observability #IBMGarage @holly_cummins

Slide 148

Slide 148

recoverability © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 149

Slide 149

unrecoverable © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 150

Slide 150

back in ms no data loss manual intervention bricked fast, but data lost handoffs © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 151

Slide 151

handoffs bad automation good © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 152

Slide 152

fail 9 microservices envy

Slide 153

Slide 153

se a b od o g a e r a s r e n i a t con © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 154

Slide 154

it’s not a competition to see how many you can have © 2019 IBM Corporation se a b od o g a e r a s r e n i a t con #IBMGarage @holly_cummins

Slide 155

Slide 155

“we’re going too slowly. we need to get rid of COBOL and make microservices!” #IBMGarage @holly_cummins

Slide 156

Slide 156

“we’re going too slowly. we need to get rid of COBOL and make microservices!” “… but our release board only meets twice a year.” #IBMGarage @holly_cummins

Slide 157

Slide 157

distributed monolith #IBMGarage @holly_cummins

Slide 158

Slide 158

distributed monolith but without compile-time checking … or guaranteed function execution #IBMGarage @holly_cummins

Slide 159

Slide 159

reasons not to do microservices small team not planning to release independently don’t want complexity of a service mesh - or worse yet, rolling your own domain model doesn’t split nicely #IBMGarage @holly_cummins

Slide 160

Slide 160

ways to succeed at cloud native © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 161

Slide 161

devops © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 162

Slide 162

be clear on what you’re trying to achieve © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 163

Slide 163

align business and IT © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 164

Slide 164

collaborate with experts co-creation is awesome © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 165

Slide 165

optimise for feedback © 2019 IBM Corporation #IBMGarage @holly_cummins

Slide 166

Slide 166

® @holly_cummins 104