"Continuous Delivery Made Possible" by Domenico Musto

1. Continuous delivery
made possible
Domenico Musto domenico.musto@gmail.com
@mimmozzo

2. 50%

3. 35%

4. What do you think about this ?

5. Continuous delivery
▪ Reduce time to market
▪ Quickly adapt your product to market/customers needs
▪ Enable experimentation
▪ Create an awesome motivated team

6. Domenico Musto
▪ Principal Engineer at Spektrix
▪ Distributed systems
▪ REST
▪ Messaging
▪ Automation testing
▪ Continuous delivery
domenico.musto@gmail.com
@mimmozzo

7. Agenda
▪ Continuous integration
▪ Continuous deployment
▪ Continuous delivery
▪ How to get there

8. Continuous integration
The process of frequently integrating the code you are
working on with everybody else’s code

9. Continuous deployment
Automatically deploy on an integration test environment the
"integrated code“.
Have a reasonable automated way of deploy software to a
production environment

10. Continuous delivery
The ability to easily and quickly ship new value/features to
customers at any point in time

11. Easily and quickly
▪ Being able to deploy in about 5 minutes in an automated fashion

12. Easily and quickly
▪ Being able to deploy in about 5 minutes in an automated fashion
▪ Being confident that the software you are deploying has passed a well defined
test suite

13. Easily and quickly
▪ Being able to deploy in about 5 minutes in an automated fashion
▪ Being confident that the software you are deploying has passed a well defined
test suite
▪ Being able to immediately collect info about the new version of the software

14. Easily and quickly
▪ Being able to deploy in about 5 minutes in an automated fashion
▪ Being confident that the software you are deploying has passed a well defined
test suite
▪ Being able to immediately collect info about the new version of the software
▪ Being able to quickly rollback to the previous version in a matter of minutes in an
automated fashion

15. Continuous integration
+
Continuous deployment
=
Continuous delivery

17. Maybe you didn’t know that..
▪ Continuous delivery is not suitable for every business

18. Maybe you didn’t know that..
▪ Continuous delivery is not suitable for every business
▪ It’s a cultural change

19. Maybe you didn’t know that..
▪ Continuous delivery is not suitable for every business
▪ It’s a cultural change
▪ It takes time and it will hurt you

20. How do I get there ?
▪ Kill the monolith
▪ Enable continuous integration
▪ Enable continuous deployment
▪ Process and team structure

21. Continuous integration

22. Trunk based development

23. Trunk based development
▪ Pair programming over the pull request model

24. Trunk based development
▪ Pair programming over the pull request model
▪ Features toggle

25. Trunk based development
▪ Pair programming over the pull request model
▪ Features toggle
▪ Branching by abstraction over feature branching

26. Feature branching
vs
branching by abstraction

27. Branching by
abstraction
By Martin Fowler

28. Branching by
abstraction
By Martin Fowler

29. Branching by
abstraction
By Martin Fowler

30. Branching by
abstraction
By Martin Fowler

31. Solid testing strategy

32. Integration pipeline
Code
changeDev
Run
tests
locally
Dev CommitDev
Build
and
test
CI Create
artefactCI

33. Continuous deployment

34. Deployment pipeline

35. Smart packages

36. Database
▪ Database schema as source code
▪ Migration scripts are generated, not stored
▪ Database schema works with 2 versions of the software
▪ Spread breaking changes across multiple deployments

37. Infrastructure
▪ Blue green deployment

38. Infrastructure
▪ Blue green deployment
▪ Infrastructure as code

39. Infrastructure
▪ Blue green deployment
▪ Infrastructure as code
▪ Tooling

40. Decouple release from deployment
▪ Delivery is not deployment (it may require manual intervention)

41. Decouple release from deployment
▪ Delivery is not deployment (it may require manual intervention)
▪ Feature toggles

42. Process and team structure

43. Process and team structure
▪ Create cross functional autonomous teams

44. Process and team structure
▪ Create cross functional autonomous teams
▪ Product authority within the team

45. Process and team structure
▪ Create cross functional autonomous teams
▪ Product authority within the team
▪ QAs embedded in the team

46. Process and team structure
▪ Create cross functional autonomous teams
▪ Product authority within the team
▪ QAs embedded in the team
▪ build quality in over than testing at the end

47. Process and team structure
▪ Create cross functional autonomous teams
▪ Product authority within the team
▪ QAs embedded in the team
▪ build quality in over than testing at the end
▪ close to the code and the architecture to advise on best testing strategy

48. Process and team structure
▪ Create cross functional autonomous teams
▪ Product authority within the team
▪ QAs embedded in the team
▪ build quality in over than testing at the end
▪ close to the code and the architecture to advise on best testing strategy
▪ Avoid cross teams code reviews and pull requests

49. Summary
▪ Enable continuous integration (step by step)
▪ Adopt trunk based development
▪ Integration pipeline
▪ Artefacts
▪ Enable continuous deployment (step by step)
▪ Deploy pipeline
▪ Smart packages
▪ Infrastructure as code
▪ Adjust the process (step by step)
▪ Create autonomous teams
▪ Create a shared testing strategy

50. Continuous delivery
▪ Reduce time to market
▪ Quickly adapt your product to market/customers needs
▪ Enable experimentation
▪ Create an awesome motivated team

51. “Continuous delivery doesn't have to
mean new features in prod every
minute. It's about making releases a
non-event.”
Suzie Prince

52. Thanks.
domenico.musto@gmail.com
@mimmozzo