1 / 61

Architecting for Continuous Delivery

Discover the secrets behind the architectural traits that enable a successful Continuous Delivery capability. We will explore some architectural choices architects and lead developers must make and the outcome of those decisions. We will use some real world examples of architectures created specifically to make Continuous Delivery a reality.

thekua
Télécharger la présentation

Architecting for Continuous Delivery

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. About Me @patkua

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

  4. works for About Me @patkua

  5. People who work with About Me

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

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

  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? “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” 13

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

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

  16. BUT HOW? 16

  17. PRINCIPLES 17

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

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

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

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

  22. CONWAY’S LAW IN ACTION 22

  23. CONWAY’S LAW REAL LIFE EXAMPLES 23

  24. Development Production 24

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

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

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

  28. *ilities that matter

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

  30. AUTOMATE ALL THE THINGS 30

  31. Architect for testability 31

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

  33. Y-U-NO DEPLOY? 33

  34. Architect for Configurability 34

  35. Architect for Monitorability 35

  36. Architect for Evolvability 36

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

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

  39. Post Release 1 39

  40. Reality 40

  41. Things go wrong 41

  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. 1 or 2 builds per year Porting code Manual Testing Production Support Detailed Planning 2008 50

More Related