Designing for Continuous Delivery

Talk from JDays 2013

Transcript

1. @ivar_grimstad Designing for Continuous Delivery
 Ivar Grimstad jDays 2013
2. @ivar_grimstad Ivar Grimstad Software Architect at Cybercom Sweden About the Speaker jDays 2013
3. @ivar_grimstad • The Concept of Continuous Delivery • Designing for Continuous Delivery – Techniques – Demo • Summary Contents jDays 2013
4. @ivar_grimstad Agile Manifesto jDays 2013 ! ! Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
5. @ivar_grimstad Principles behind the Agile Manifesto jDays 2013 Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. ! Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. ! Business people and developers must work together daily throughout the project. ! Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. ! The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. ! Working software is the primary measure of progress. ! Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. ! ! Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
6. @ivar_grimstad Continuous Delivery jDays 2013 A pattern language used in software development to automate and improve the process of software delivery
7. @ivar_grimstad • Every change should trigger the feedback process • Fast Feedback • Act on the Feedback Continuous Delivery jDays 2013
8. @ivar_grimstad • Build Binaries Once • One Process Deploy • Test Deployments • Flow • Fail -> Stop the Line The Deployment Pipeline jDays 2013
9. @ivar_grimstad The Deployment Pipeline jDays 2013
10. @ivar_grimstad The Deployment Pipeline jDays 2013
11. @ivar_grimstad The Book jDays 2013
12. @ivar_grimstad Designing for Continuous Delivery jDays 2013
13. @ivar_grimstad Every commit is a potential release Principle jDays 2013 Goal Keep System Releasable
14. @ivar_grimstad Feature Branches jDays 2013 Source: http://martinfowler.com/bliki/FeatureBranch.html
15. @ivar_grimstad • Blue/Green Deployments • Canary Releasing • Feature Toggles • Branch by Abstraction Techniques jDays 2013
16. @ivar_grimstad • Two identical environments • New version running alongside existing • Switch when ready Blue/Green Deployments jDays 2013
17. @ivar_grimstad Blue/Green Deployments jDays 2013
18. @ivar_grimstad Blue/Green Deployments jDays 2013
19. @ivar_grimstad Canary Releasing jDays 2013
20. @ivar_grimstad Canary Releasing jDays 2013
21. @ivar_grimstad Demo jDays 2013
22. @ivar_grimstad Feature Toggles jDays 2013
23. @ivar_grimstad Branch by Abstraction jDays 2013 A pattern for making large-scale changes to your application incrementally on mainline
24. @ivar_grimstad 1. Identify Abstraction 2. Extract Interface 3. Implement Alternative 4. Switch Implementation 5. Remove Original implementation 6. (optional) Remove Interface Branch by Abstraction - steps jDays 2013
25. @ivar_grimstad Online Cook Book – Web UI – REST API Demo Application jDays 2013
26. @ivar_grimstad Demo Application Data Model jDays 2013
27. @ivar_grimstad Demo Application Architecture jDays 2013
28. @ivar_grimstad Replace database with datastore accessed through a WebSocket API. The Task jDays 2013
29. @ivar_grimstad Replace Persistence Layer jDays 2013
30. @ivar_grimstad Demo Application Architecture jDays 2013
31. @ivar_grimstad 1. Identify Abstraction 2. Extract Interface 3. Implement Alternative 4. Switch Implementation 5. Remove Original implementation 6. (optional) Remove Interface Branch by Abstraction - steps jDays 2013
32. @ivar_grimstad 1. Identify Abstraction jDays 2013
33. @ivar_grimstad 1. Identify Abstraction 2. Extract Interface 3. Implement Alternative 4. Switch Implementation 5. Remove Original implementation 6. (optional) Remove Interface Branch by Abstraction - steps jDays 2013
34. @ivar_grimstad 2. Extract Interface jDays 2013
35. @ivar_grimstad 1. Identify Abstraction 2. Extract Interface 3. Implement Alternative 4. Switch Implementation 5. Remove Original implementation 6. (optional) Remove Interface Branch by Abstraction - steps jDays 2013
36. @ivar_grimstad 3. Implement Alternative jDays 2013
37. @ivar_grimstad 1. Identify Abstraction 2. Extract Interface 3. Implement Alternative 4. Switch Implementation 5. Remove Original implementation 6. (optional) Remove Interface Branch by Abstraction - steps jDays 2013
38. @ivar_grimstad 4. Switch Implementation jDays 2013
39. @ivar_grimstad 1. Identify Abstraction 2. Extract Interface 3. Implement Alternative 4. Switch Implementation 5. Remove Original implementation 6. (optional) Remove Interface Branch by Abstraction - steps jDays 2013
40. @ivar_grimstad 5. Remove Original Implementation jDays 2013
41. @ivar_grimstad 1. Identify Abstraction 2. Extract Interface 3. Implement Alternative 4. Switch Implementation 5. Remove Original implementation 6. (optional) Remove Interface Branch by Abstraction - steps jDays 2013
42. @ivar_grimstad 6. (optional) Remove Interface jDays 2013
43. @ivar_grimstad 1. Identify Abstraction 2. Extract Interface 3. Implement Alternative 4. Switch Implementation 5. Remove Original implementation 6. (optional) Remove Interface Branch by Abstraction - recap jDays 2013
44. @ivar_grimstad • Blue/Green Deployments • Canary Releasing • Feature Toggles • Branch by Abstraction Summary of Techniques jDays 2013 Environment Code
45. @ivar_grimstad • Consider multiple environments • Branch by Abstraction is a powerful technique • Identify abstractions as early as possible • Extract interfaces where appropriate Summary jDays 2013
46. @ivar_grimstad jDays 2013