The Road to Continuous Deployment: A Case Study (Bosnia Agile Day 2017)

It's a situation many of us are familiar with: a large legacy, monolithic application, limited or no tests, slow & manual release process, low velocity, no confidence... A lot of refactoring is required, but management keeps pushing for new features.

How to proceed?

Using examples and lessons learned from a real-world case, I'll show you how to replace a legacy application with a modern service-oriented architecture and build a continuous integration and deployment pipeline to deliver value from the first sprint. On the way, we’ll take a look at the process, automated testing, monitoring, master/trunk based development and various tips and best practices.

Transcript

1. THE ROAD TO CONTINUOUS DEPLOYMENT - A CASE STUDY MICHIEL ROOK @michieltcs
2. ▸ Developer, consultant, trainer, speaker ▸ @michieltcs
4. @michieltcs
5. @michieltcs Large aging monolith
6. @michieltcs Large aging monolith Generates income
7. @michieltcs Large aging monolith Slow & complex Generates income
8. @michieltcs Large aging monolith Slow & complex Generates income Technical debt
9. @michieltcs
10. @michieltcs Manual releases
11. @michieltcs Manual releases Fragile tests
12. @michieltcs Manual releases Frequent issues Fragile tests
13. @michieltcs Manual releases Frequent issues Fragile tests Low velocity
14. GOALS @michieltcs
15. GOALS REDUCE
 ISSUES 1 @michieltcs
16. GOALS REDUCE
 ISSUES REDUCE
 LEAD TIME 1 2 @michieltcs
17. GOALS REDUCE
 ISSUES REDUCE
 LEAD TIME INCREASE PRODUCTIVITY 1 2 3 @michieltcs
18. GOALS REDUCE
 ISSUES REDUCE
 LEAD TIME INCREASE PRODUCTIVITY INCREASE MOTIVATION 1 2 3 4 @michieltcs
19. REFACTOR? REBUILD?
20. APPROACH ▸ API first ▸ Services per domain object (job, jobseeker, ...) ▸ Migrate individual pages @michieltcs
21. ORIGINAL MONOLITH DB @michieltcs
22. ORIGINAL MONOLITH PROXY SERVICE ORIGINAL MONOLITH DB DB DB @michieltcs
23. ORIGINAL MONOLITH PROXY SERVICE ORIGINAL MONOLITH ORIGINAL MONOLITH SERVICE SERVICE SERVICE PROXY DB DB DB DB DB DB @michieltcs
24. ARCHITECTURE FRONTENDS ARE SERVICES @michieltcs
25. ARCHITECTURE FRONTENDS ARE SERVICES SERVICES BEHIND LOAD BALANCERS @michieltcs
26. ARCHITECTURE FRONTENDS ARE SERVICES SERVICES BEHIND LOAD BALANCERS ACCESS LEGACY DB'S @michieltcs
27. ARCHITECTURE FRONTENDS ARE SERVICES SERVICES BEHIND LOAD BALANCERS ACCESS LEGACY DB'S SERVICES IN CONTAINERS @michieltcs
28. IMPROVING
29. CONTINUOUS EVERYTHING
30. DEV BUILD / TEST CONTINUOUS INTEGRATION @michieltcs
31. DEV BUILD / TEST ACCEPTANCE PRODUCTION CONTINUOUS DELIVERY @michieltcs
32. DEV BUILD / TEST STAGING / ACCEPTANCE PRODUCTION CONTINUOUS DEPLOYMENT @michieltcs
33. EVERY COMMIT GOES TO PRODUCTION
34. IF IT HURTS DO IT MORE OFTEN
35. SMALL STEPS @michieltcs
36. SMALL STEPS EARLY FEEDBACK @michieltcs
37. SMALL STEPS EARLY FEEDBACK REDUCE TIME TO RECOVER @michieltcs
38. SMALL STEPS EXPERIMENTS! EARLY FEEDBACK REDUCE TIME TO RECOVER @michieltcs
39. ONLY COMMIT TO MASTER
40. NO BRANCHES
41. NO BRANCHES REALLY.
44. DELAYING INTEGRATION
45. CONFLICTS
46. FEATURE TOGGLES
47. DECOUPLE DEPLOYMENTS
 FROM RELEASES
48. @michieltcs
49. FEATURE TOGGLE DEBT
50. CODE REVIEWS?
51. PAIR PROGRAMMING
52. CONTINUOUS INLINE CODE REVIEW
53. DEVOPS
54. DEVSECOPS
55. DEVSECQAOPS
56. DEVSECQABIZOPS
57. DEVSECQABIZNETOPS
58. DEVSECQABIZSYSNETOPS
59. DEVTESTSECQABIZSYSNETOPS
60. DEV*OPS
61. TEAM BUILDS IT
62. TEAM RUNS IT
63. TEAM IMPROVES IT
64. TEAM IS RESPONSIBLE
65. BUILD PIPELINE
66. CONNECT THE DOTS
67. AUTOMATE REPEATABLE THINGS
68. CONTINUOUS TESTING
69. CONFIDENCE
70. DEFENSE IN DEPTH UNIT TESTS INTEGRATION
 TESTS ACCEPTANCE
 TESTS UI TESTS @michieltcs
71. DEFENSE IN DEPTH UNIT TESTS INTEGRATION
 TESTS ACCEPTANCE UI TESTS @Test
 public void jobCannotBeFound() {
 when(jobRepository.getById(EXPECTED_JOB_ID))
 .thenReturn(null);
 
 JobService jobService = new JobService(jobRepository);
 
 assertNull(jobService.getById(EXPECTED_JOB_ID));
 verify(jobRepository).getById(EXPECTED_JOB_ID);
 } @michieltcs
72. DEFENSE IN DEPTH UNIT TESTS INTEGRATION
 TESTS ACCEPTANCE
 TESTS UI TESTS @Test
 public void shouldFindJob() {
 expectedJob = loadFixture('active_job.yml');
 actualJob = repository.getById(expectedJob.getId());
 
 assertThat(actualJob, isA(Job.class));
 assertEquals(expectedJob.getId(), actualJob.getId());
 } @michieltcs
73. DEFENSE IN DEPTH UNIT TESTS INTEGRATION
 TESTS ACCEPTANCE
 TESTS UI TESTS Scenario: Link to related job
 Given a job exists
 And there are related jobs available
 When that job is viewed
 Then a list of related jobs is shown
 And each related job links to the detail page of the related job @michieltcs
74. DEFENSE IN DEPTH UNIT TESTS INTEGRATION
 TESTS ACCEPTANCE
 TESTS UI TESTS @michieltcs
75. UNIT TESTS INTEGRATION TESTS ACCEPTANCE TESTS UI TESTS SMOKE
 TESTS Cost Speed Exploratory
 testing Monitoring @michieltcs
76. GOOD ENOUGH
77. PIPELINE SPEED = KEY
78. ROLLING UPDATE
79. LOAD BALANCER ROLLING UPDATE SERVICE V1.0 SERVICE V1.0 SERVICE V1.0 @michieltcs
80. LOAD BALANCER ROLLING UPDATE SERVICE V1.0 SERVICE V1.0 SERVICE V1.0 SERVICE V1.1 @michieltcs
81. LOAD BALANCER ROLLING UPDATE SERVICE V1.0 SERVICE V1.1 SERVICE V1.0 SERVICE V1.0 @michieltcs
82. LOAD BALANCER ROLLING UPDATE SERVICE V1.0 SERVICE V1.1 SERVICE V1.0 SERVICE V1.1 @michieltcs
83. LOAD BALANCER ROLLING UPDATE SERVICE V1.0 SERVICE V1.1 SERVICE V1.1 SERVICE V1.0 @michieltcs
84. LOAD BALANCER ROLLING UPDATE SERVICE V1.0 SERVICE V1.1 SERVICE V1.1 SERVICE V1.1 @michieltcs
85. LOAD BALANCER ROLLING UPDATE SERVICE V1.1 SERVICE V1.1 SERVICE V1.1 SERVICE V1.0 @michieltcs
86. LOAD BALANCER ROLLING UPDATE SERVICE V1.1 SERVICE V1.1 SERVICE V1.1 @michieltcs
87. PIPELINE AS CODE node {
 stage('Run tests') {
 sh "phpunit"
 sh "behat"
 }
 
 stage('Build docker image') {
 sh "docker build -t jobservice:${env.BUILD_NUMBER} ."
 sh "docker push jobservice:${env.BUILD_NUMBER}"
 }
 
 stage('Deploy staging') {
 sh "ansible-playbook -e BUILD=${env.BUILD_NUMBER}
 -i staging deploy.yml"
 }
 
 stage('Deploy production') {
 sh "ansible-playbook -e BUILD=${env.BUILD_NUMBER}
 -i prod deploy.yml"
 }
 } @michieltcs
88. @michieltcs
89. FEEDBACK!
90. RESULTS
91. @michieltcs Team acceptance
92. Feature toggle cap @michieltcs Team acceptance
93. Feature toggle cap Business alignment & agility @michieltcs Team acceptance
94. Feature toggle cap Business alignment & agility Focus on replacing legacy @michieltcs Team acceptance
95. Reduced number of issues 1 @michieltcs
96. Reduced number of issues 1 Build time
 < 10 min.
 (50+ per day) 2 4 @michieltcs
97. Reduced number of issues 1 Build time
 < 10 min.
 (50+ per day) Improved metrics & audience statistics 2 3 @michieltcs
98. Reduced number of issues 1 Build time
 < 10 min.
 (50+ per day) Improved metrics & audience statistics Increased confidence, velocity & fun 2 3 4 @michieltcs
99. Reduce cycle times. React faster to the market and test product ideas. Make things! We make Agile, DevOps and Continuous Delivery accessible! Hands-on, results- oriented approach to get you where you need to be. Modern infrastructure and pipelines in minutes.
100. THANK YOU! @michieltcs / mrook@fourscouts.nl www.michielrook.nl