CodeCamp23 Enabling Microservice Success

Slide 1

Slide 1 text

@sarahjwells@mastodon.social Enabling Microservice Success Sarah Wells

Slide 2

Slide 2 text

@sarahjwells@mastodon.social Enabling Microservice Success Sarah Wells

Slide 3

Slide 3 text

@sarahjwells@mastodon.social

Slide 4

Slide 4 text

@sarahjwells@mastodon.social

Slide 5

Slide 5 text

@sarahjwells@mastodon.social

Slide 6

Slide 6 text

@sarahjwells@mastodon.social What does a successful software development organisation look like?

Slide 7

Slide 7 text

@sarahjwells@mastodon.social

Slide 8

Slide 8 text

@sarahjwells@mastodon.social Accelerate deﬁnes performance in terms of the impact on the productivity, proﬁtability and market share of your business, compared to competitors

Slide 9

Slide 9 text

@sarahjwells@mastodon.social Four outcomes that link to high performance: ● short lead time ● high deployment frequency ● low change fail percentage ● short mean time to restore

Slide 10

Slide 10 text

@sarahjwells@mastodon.social Accelerate's key capabilities (Forsgren, Humble, Kim)

Slide 11

Slide 11 text

@sarahjwells@mastodon.social ● Regularly delivering real business value

Slide 12

Slide 12 text

@sarahjwells@mastodon.social 1. Regularly delivering real business value 2. Adapting to change 3. Maintaining appropriate service levels 4. Spending most of your time on meaningful work 5. Not having to start again 6. Keeping risk to an acceptable level

Slide 13

Slide 13 text

@sarahjwells@mastodon.social Reasons to choose microservices

Slide 14

Slide 14 text

@sarahjwells@mastodon.social Microservices are a solution to an organisational problem

Slide 15

Slide 15 text

@sarahjwells@mastodon.social Reasons to use microservices ● Because loose coupling supports ﬂow

Slide 16

Slide 16 text

@sarahjwells@mastodon.social Reasons to use microservices ● Because loose coupling supports ﬂow ● For the developer experience

Slide 17

Slide 17 text

@sarahjwells@mastodon.social Reasons to use microservices ● Because loose coupling supports ﬂow ● For the developer experience ● Aids compliance and security

Slide 18

Slide 18 text

@sarahjwells@mastodon.social Reasons to use microservices ● Because loose coupling supports ﬂow ● For the developer experience ● Aids compliance and security ● Scaling only where needed

Slide 19

Slide 19 text

@sarahjwells@mastodon.social Reasons to use microservices ● Because loose coupling supports ﬂow ● For the developer experience ● Aids compliance and security ● Scaling only where needed ● Increased robustness

Slide 20

Slide 20 text

Slide 21

Slide 21 text

@sarahjwells@mastodon.social

Slide 22

Slide 22 text

@sarahjwells@mastodon.social Challenges

Slide 23

Slide 23 text

@sarahjwells@mastodon.social Challenges ● Estate complexity

Slide 24

Slide 24 text

@sarahjwells@mastodon.social Challenges ● Estate complexity ● Operational complexity

Slide 25

Slide 25 text

@sarahjwells@mastodon.social Challenges ● Estate complexity ● Operational complexity ● Finding the right granularity

Slide 26

Slide 26 text

@sarahjwells@mastodon.social Challenges ● Estate complexity ● Operational complexity ● Finding the right granularity ● Handling change

Slide 27

Slide 27 text

@sarahjwells@mastodon.social Challenges ● Estate complexity ● Operational complexity ● Finding the right granularity ● Handling change ● Developer experience is very different

Slide 28

Slide 28 text

@sarahjwells@mastodon.social Challenges ● Estate complexity ● Operational complexity ● Finding the right granularity ● Handling change ● Developer experience is very different ● Organisational change

Slide 29

Slide 29 text

@sarahjwells@mastodon.social Conditions for Success

Slide 30

Slide 30 text

@sarahjwells@mastodon.social Challenges ● Domain understanding

Slide 31

Slide 31 text

@sarahjwells@mastodon.social Challenges ● Domain understanding ● Products not projects

Slide 32

Slide 32 text

@sarahjwells@mastodon.social Challenges ● Domain understanding ● Products not projects ● Leadership support

Slide 33

Slide 33 text

@sarahjwells@mastodon.social Challenges ● Domain understanding ● Products not projects ● Leadership support ● Teams that want autonomy

Slide 34

Slide 34 text

@sarahjwells@mastodon.social Challenges ● Domain understanding ● Products not projects ● Leadership support ● Teams that want autonomy ● Support for that autonomy

Slide 35

Slide 35 text

@sarahjwells@mastodon.social Challenges ● Domain understanding ● Products not projects ● Leadership support ● Teams that want autonomy ● Support for that autonomy ● Technical maturity

Slide 36

Slide 36 text

Slide 37

Slide 37 text

@sarahjwells@mastodon.social 1. Regularly delivering real business value

Slide 38

Slide 38 text

@sarahjwells@mastodon.social Four outcomes that link to high performance: ● short lead time ● high deployment frequency ● low change fail percentage ● short mean time to restore

Slide 39

Slide 39 text

@sarahjwells@mastodon.social

Slide 40

Slide 40 text

@sarahjwells@mastodon.social Accelerate's key capabilities (Forsgren, Humble, Kim)

Slide 41

Slide 41 text

@sarahjwells@mastodon.social 2. Adapting to change

Slide 42

Slide 42 text

@sarahjwells@mastodon.social Changing business priorities

Slide 43

Slide 43 text

@sarahjwells@mastodon.social

Slide 44

Slide 44 text

@sarahjwells@mastodon.social Changing technology

Slide 45

Slide 45 text

@sarahjwells@mastodon.social

Slide 46

Slide 46 text

@sarahjwells@mastodon.social "For many years, the tongue-in-cheek deﬁnition of software architecture was “the stuff that’s hard to change later.” Later, the microservices architecture style appeared, where change is a ﬁrst-class design consideration." From the preface of Fundamentals of Software Architecture, Mark Richards and Neal Ford

Slide 47

Slide 47 text

@sarahjwells@mastodon.social Beware the "long tail"

Slide 48

Slide 48 text

@sarahjwells@mastodon.social 3. Maintaining appropriate service levels

Slide 49

Slide 49 text

@sarahjwells@mastodon.social Four outcomes that link to high performance: ● short lead time ● high deployment frequency ● low change fail percentage ● short mean time to restore

Slide 50

Slide 50 text

@sarahjwells@mastodon.social Optimising for a short mean time to restore

Slide 51

Slide 51 text

@sarahjwells@mastodon.social Loose coupling = small blast radius

Slide 52

Slide 52 text

@sarahjwells@mastodon.social https://lamport.azurewebsites.net/pubs/distributed-system.txt “A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable”

Slide 53

Slide 53 text

@sarahjwells@mastodon.social Richard I Cook - https://www.adaptivecapacitylabs.com/ HowComplexSystemsFail.pdf

Slide 54

Slide 54 text

@sarahjwells@mastodon.social Richard I Cook - https://www.adaptivecapacitylabs.com/ HowComplexSystemsFail.pdf Distributed systems need to be built with multiple layers of defense against failure

Slide 55

Slide 55 text

@sarahjwells@mastodon.social Build resilience in

Slide 56

Slide 56 text

@sarahjwells@mastodon.social

Slide 57

Slide 57 text

@sarahjwells@mastodon.social

Slide 58

Slide 58 text

@sarahjwells@mastodon.social Know when something important is broken

Slide 59

Slide 59 text

@sarahjwells@mastodon.social Checks running in January 2021 at the Financial Times

Slide 60

Slide 60 text

@sarahjwells@mastodon.social

Slide 61

Slide 61 text

@sarahjwells@mastodon.social

Slide 62

Slide 62 text

@sarahjwells@mastodon.social Focus on business capabilities

Slide 63

Slide 63 text

@sarahjwells@mastodon.social Monitor your business capabilities

Slide 64

Slide 64 text

@sarahjwells@mastodon.social Work out what's going on

Slide 65

Slide 65 text

@sarahjwells@mastodon.social Monitoring is not enough

Slide 66

Slide 66 text

@sarahjwells@mastodon.social Observability: can you infer what’s going on in the system by looking at external outputs?

Slide 67

Slide 67 text

@sarahjwells@mastodon.social Tracing events through your system

Slide 68

Slide 68 text

@sarahjwells@mastodon.social

Slide 69

Slide 69 text

@sarahjwells@mastodon.social 4. Spending most of your time on meaningful work

Slide 70

Slide 70 text

@sarahjwells@mastodon.social Autonomous teams have a lot of things to know about

Slide 71

Slide 71 text

@sarahjwells@mastodon.social Maintaining microservices means constant work

Slide 72

Slide 72 text

@sarahjwells@mastodon.social Product development teams can’t be completely autonomous

Slide 73

Slide 73 text

@sarahjwells@mastodon.social Platform engineering

Slide 74

Slide 74 text

@sarahjwells@mastodon.social Platform engineering Engineering Enablement

Slide 75

Slide 75 text

@sarahjwells@mastodon.social Paving the road

Slide 76

Slide 76 text

@sarahjwells@mastodon.social https://charity.wtf/2018/12/02/software-sprawl-the-golden-p ath-and-scaling-teams-with-agency/

Slide 77

Slide 77 text

@sarahjwells@mastodon.social ● Self service ● Well-documented ● Discoverable

Slide 78

Slide 78 text

@sarahjwells@mastodon.social 5. Not having to start again

Slide 79

Slide 79 text

@sarahjwells@mastodon.social Without work, systems get messy

Slide 80

Slide 80 text

@sarahjwells@mastodon.social Starting again is appealing!

Slide 81

Slide 81 text

@sarahjwells@mastodon.social Rebuilding stops you delivering value

Slide 82

Slide 82 text

@sarahjwells@mastodon.social ● £10 million ● 2 years in maintenance mode

Slide 83

Slide 83 text

@sarahjwells@mastodon.social Microservices *should* make it easy

Slide 84

Slide 84 text

@sarahjwells@mastodon.social "Habitability is the characteristic of source code that enables people coming to the code later in its life to understand its construction and intentions and to change it comfortably and conﬁdently." Habitability and Piecemeal Growth, Richard P Gabriel, https://www.dreamsongs.com/Files/PatternsOfSoftware.pdf

Slide 85

Slide 85 text

@sarahjwells@mastodon.social 6. Keeping risk to an acceptable level

Slide 86

Slide 86 text

@sarahjwells@mastodon.social Know your estate

Slide 87

Slide 87 text

@sarahjwells@mastodon.social https://www.infoq.com/presentations/productivity-ft/

Slide 88

Slide 88 text

@sarahjwells@mastodon.social Active ownership

Slide 89

Slide 89 text

@sarahjwells@mastodon.social Services need to be actively owned, by a team

Slide 90

Slide 90 text

@sarahjwells@mastodon.social

Slide 91

Slide 91 text

@sarahjwells@mastodon.social Be ﬂexible on tech choices only where you need to be

Slide 92

Slide 92 text

@sarahjwells@mastodon.social The paved road allows you to make global decisions around risk

Slide 93

Slide 93 text

@sarahjwells@mastodon.social ● Safe ● Secure ● Reliable by default

Slide 94

Slide 94 text

@sarahjwells@mastodon.social Guardrails and governance

Slide 95

Slide 95 text

@sarahjwells@mastodon.social The FT’s guardrails

Slide 96

Slide 96 text

@sarahjwells@mastodon.social

Slide 97

Slide 97 text

@sarahjwells@mastodon.social log4shell

Slide 98

Slide 98 text

@sarahjwells@mastodon.social What next for microservices? https://thenewstack.io/the-future-of-microservices-more-abstr actions/

Slide 99

Slide 99 text

@sarahjwells@mastodon.social https://thenewstack.io/the-future-of-microservices-more-abstr actions/ We have mature well-designed microservice frameworks

Slide 100

Slide 100 text

@sarahjwells@mastodon.social https://thenewstack.io/the-future-of-microservices-more-abstr actions/ Open telemetry provides a standard for distributed telemetry data

Slide 101

Slide 101 text

@sarahjwells@mastodon.social Improving developer experience is the next challenge

Slide 102

Slide 102 text

@sarahjwells@mastodon.social https://thenewstack.io/the-future-of-microservices-more-abstr actions/

Slide 103

Slide 103 text

@sarahjwells@mastodon.social Daniel Bryant, quoted in https://thenewstack.io/ the-future-of-microservices-more-abstractions/ “companies.. are creating a Heroku-like CLI for their developers, so that a command like ‘create new microservice’ spins up some scaffolding, plugs into CI, plugs into pipelines, plugs into observability”

Slide 104

Slide 104 text

@sarahjwells@mastodon.social https://backstage.io/

Slide 105

Slide 105 text

@sarahjwells@mastodon.social https://redmonk.com/jgovernor/2022/02/21/what-is-developer -experience-a-roundup-of-links-and-goodness/ “organisations want developers to spend more time coding and less time thinking about and working on infrastructure”

Slide 106

Slide 106 text

@sarahjwells@mastodon.social https://redmonk.com/jgovernor/2022/02/21/what-is-developer -experience-a-roundup-of-links-and-goodness/ “Why would a developer put up with a poor developer experience when they can likely ﬁnd a job that better aligns with their needs and preferences?”

Slide 107

Slide 107 text

@sarahjwells@mastodon.social Wrapping up…

Slide 108

Slide 108 text

@sarahjwells@mastodon.social Fast ﬂow is important

Slide 109

Slide 109 text

@sarahjwells@mastodon.social Which means you need: ● zero-downtime deployments ● loose coupling

Slide 110

Slide 110 text

@sarahjwells@mastodon.social Microservices reduce build & deploy complexity and increase operational complexity

Slide 111

Slide 111 text

@sarahjwells@mastodon.social Autonomy comes with responsibility Jason Yip, Thoughts on the Spotify model, https://jchyip.medium.com/my- critique-of-the-spotify-model-part-1-197d335ef7af

Slide 112

Slide 112 text

@sarahjwells@mastodon.social You need some scaffolding

Slide 113

Slide 113 text

@sarahjwells@mastodon.social Everything is a bit distributed now

Slide 114

Slide 114 text

@sarahjwells@mastodon.social https://www.oreilly.com/library/view/enabling-microservice-su ccess/9781098130787/

Slide 115

Slide 115 text

@sarahjwells@mastodon.social Slides: https://speakerdeck/sarahwells/code-camp23- enabling-microservice-success Contact: @sarahwells@mastodon.social https://www.linkedin.com/in/sarahjwells1/