1.
ARCHITECTING FOR
CONTINUOUS DELIVERY
Patrick Kua (@patkua)
1

2.
About Me
@patkua

3.
About Me
@patkua
wrote
http://tiny.cc/twtlhttp://tiny.cc/retros

4.
About Me
@patkua
works for

5.
About Me
People who work with

6.
About Me
People who work with
wrote the book on

7.
OUR AGENDA
7
What is CD (briefly)
Architectural Principles
Case Study
Challenges

8.
WHAT IS CONTINUOUS DELIVERY?
8

9.
WHAT IS CONTINUOUS DELIVERY?
9

10.
WHAT IS CONTINUOUS DELIVERY?
10

11.
WHAT IS CONTINUOUS DELIVERY?
11

12.
WHAT IS CONTINUOUS DELIVERY?
12

13.
WHAT IS CONTINUOUS DELIVERY?
13
“Our highest priority is to satisfy the
customer through early and
continuous delivery
of valuable software.”

14.
WHAT IS CONTINUOUS DELIVERY?
14
The capability to reliably
release software to
production on demand
(with confidence)

15.
WHAT IS CONTINUOUS DELIVERY?
15
Continuous
Integration
Releasable
Artefact
Continuous
Deployment
Automatic
releases
Continuous
Delivery
Releases
on demand

16.
BUT HOW?
16

17.
PRINCIPLES
17

18.
PRINCIPLES
18
The one law to rule them all…

19.
19
The one law to rule them all…
CONWAY’S LAW

20.
20
The one law to rule them all…
CONWAY’S LAW
“organizations which design systems ... are
constrained to produce designs which are copies
of the communication structures of these
organizations"

21.
21
“If you have 4 groups working on a
compiler, you’ll get a 4-pass compiler”
Eric Raymond - Hacker’s Bible, 1996

22.
CONWAY’S LAW IN ACTION
22

23.
23
CONWAY’S LAW
REAL LIFE EXAMPLES

24.
Production
24
Development

25.
Production
25
Development
Tooling
Culture
Incentives
A divide in:

26.
26
- Werner Voegls (Amazon)
“You build it,
you run it”

27.
PRINCIPLES
27
The one law to rule them all…
-ilities that matter

28.
*ilities that matter

29.
Automatability
Configurability
Testability
Deployability
Evolvability
Monitorability
*ilities that matter

30.
30
AUTOMATE
ALL THE THINGS

31.
31
Architect for testability

32.
32
“Fear is the path to the dark side. Fear leads
to anger. Anger leads to hate. Hate leads to
suffering.” - Yoda

33.
33
Y-U-NO DEPLOY?

34.
34
Architect for Configurability

35.
35
Architect for Monitorability

36.
36
Architect for Evolvability

37.
37
Evolutionary Architecture
Technology Radar
Jan 2010
Aug 2010
Jan 2011
Jul 2011
Mar 2012
Assess
Trial
Trial
Adopt
Adopt

38.
PRINCIPLES
38
The one law to rule them all…
-ilities that matter
Iterate

39.
39
Post Release 1

40.
40
Reality

41.
41
Things go wrong

42.
CASE STUDY: CLIENT
42

43.
16+programme
streams

44.
4 Product Owners

45.
Constraints

46.
What we did

47.
The result

48.
CASE STUDY: HP
48

49.
49

50.
50
2008
1 or 2 builds per year
Porting code
Manual Testing
Production Support
Detailed Planning

51.
51
Common codebase
Automated testing
Stop the line
Architecture change

52.
52
2011
10-15 builds per day
Automated test maintenance
New automated tests
1 master + 1 branch

53.
Who is doing Continuous Delivery?

54.
CHALLENGES
54

55.
Production
55
Development

56.
56
Snowflake servers

57.
57
Configuration Management

58.
Investment

59.
Mindset

60.
CONCLUSION
60

61.
61
QUESTIONS
@patkua