Pat Hermens - From 100 to 1,000+ deployments a day - Codemotion Amsterdam 2019
•Download as PPTX, PDF•
0 likes•249 views
Coolblue is a proud Dutch company, with a large internal development department; one that truly takes CI/CD to heart. Empowerment through automation is at the heart of these development teams, and with more than 1000 deployments a day, we think it's working out quite well. In this session, Pat Hermens (a Development Managers) will step you through what enables us to move so quickly, which tools we use, and most importantly, the mindset that is required to enable development teams to deliver at such a rapid pace.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Pat Hermens - From 100 to 1,000+ deployments a day - Codemotion Amsterdam 2019
Similar to Pat Hermens - From 100 to 1,000+ deployments a day - Codemotion Amsterdam 2019 (20)
More from Codemotion
More from Codemotion (20)
Recently uploaded
Recently uploaded (20)
Pat Hermens - From 100 to 1,000+ deployments a day - Codemotion Amsterdam 2019
- 1. From 100 to 1000+ deployments a day Pat Hermens Amsterdam | April 2-3, 2019
- 2. From 100 to 1,000+ deployments What does it take to get to the next level?
- 3. Pat Hermens Development Manager Coding for 15+ years Father & husband Rotterdam, Netherlands @phermens pat@coolblue.nl
- 15. 100 / 1,000 / 10,000; so what?
- 17. … Apparently we are too much trained to disregard differences in scale, to treat them as “gradual differences that are not essential.” We tell ourselves that what we can do once, we can also do twice and by induction, we fool ourselves into believing that we can do it as many times as needed, but this is just not true! — Edsger Dijkstra, 1969
- 19. Prerequisites...
- 21. 23 @phermens The “faster to master” checklist Developing ⬜ Coding guidelines ⬜ Code reviews ⬜ Code analysis ⬜ Short-lived branches ⬜ Feature toggles Monitoring ⬜ Defined key metrics ⬜ Measure – create dashboards ⬜ Proactivity – add alerting (& act!) Testing ⬜ Unit tests ⬜ Module tests ⬜ Integration tests ⬜ End-to-end tests ⬜ Test automation Deploying ⬜ Continuous Integration ⬜ Continuous Delivery ⬜ Infrastructure as Code
- 22. 24 @phermens Developing ☑ Coding guidelines ☑ Code reviews ⬜ Code analysis ☑ Short-lived branches ⬜ Feature toggles Monitoring ☑ Defined key metrics ⬜ Measure – create dashboards ⬜ Proactivity – add alerting (& act!) Testing ☑ Unit tests ⬜ Module tests ⬜ Integration tests ⬜ End-to-end tests ☑ Test automation Deploying ☑ Continuous Integration ⬜ Continuous Delivery ⬜ Infrastructure as Code The “faster to master” checklist
- 23. 25 @phermens Developing ☑ Coding guidelines ☑ Code reviews ⬜ Code analysis ☑ Short-lived branches ☑ Feature toggles Monitoring ☑ Defined key metrics ☑ Measure – create dashboards ⬜ Proactivity – add alerting (& act!) Testing ☑ Unit tests ☑ Module tests ⬜ Integration tests ☑ End-to-end tests ☑ Test automation Deploying ☑ Continuous Integration ☑ Continuous Delivery ⬜ Infrastructure as Code The “faster to master” checklist
- 24. 26 @phermens Developing ☑ Coding guidelines ☑ Code reviews ☑ Code analysis ☑ Short-lived branches ☑ Feature toggles Monitoring ☑ Defined key metrics ☑ Measure – create dashboards ☑ Proactivity – add alerting (& act!) Testing ☑ Unit tests ☑ Module tests ☑ Integration tests ☑ End-to-end tests ☑ Test automation Deploying ☑ Continuous Integration ☑ Continuous Delivery ☑ Infrastructure as Code The “faster to master” checklist
- 25. Story time!
- 28. Responsibility
- 39. 44 @phermens
- 42. Autonomy
- 43. Autonomy
- 44. 49 @phermens Serilog + Splunk + DataDog
- 50. Autonomy
- 52. 58 @phermens
- 53. 59 @phermens
- 54. 60 @phermens
- 55. 61 @phermens $ $ $ $ $
- 56. 62 @phermens $ $ $ $ $
- 57. 63 @phermens
- 58. 64 @phermens UDP
- 59. 65 @phermens UDP
- 60. 66 @phermens UDP
- 61. 67 @phermens UDP
- 62. 68 @phermens UDP
- 63. 69 @phermens
- 64. 70 @phermens TCP
- 65. 71 @phermens TCP
- 66. 72 @phermens
- 67. 73 @phermens
- 68. 74 @phermens
- 70. 76 @phermens
- 71. 77 @phermens AWS Lambda stats for Vanessa Optima Prime (as of 2019-04-01) Last 30 days Last 7 days
- 72. 78 @phermens AWS Lambda stats for Vanessa Optima Prime (as of 2019-04-01) Last 30 days Last 7 days
- 73. 79 @phermens
- 74. 80 @phermens
- 79. 85 @phermens
- 80. 86 @phermens
- 81. 87 @phermens Development team tooling choices
- 82. 88 @phermens Infrastructure team tooling choices
- 83. 89 @phermens
- 87. 93 @phermens
- 90. 96 @phermens Fail early, fail often, but always fail forward.
- 102. NOTE: Now 50cc!
- 112. NOTE: Now 45cc!
- 115. 123 @phermens
- 116. 124 @phermens
- 121. 130 @phermens The “faster to master” checklist Developing ⬜ Coding guidelines ⬜ Code reviews ⬜ Code analysis ⬜ Short-lived branches ⬜ Feature toggles Monitoring ⬜ Defined key metrics ⬜ Measure – create dashboards ⬜ Proactivity – add alerting (& act!) Testing ⬜ Unit tests ⬜ Module tests ⬜ Integration tests ⬜ End-to-end tests ⬜ Test automation Deploying ⬜ Continuous Integration ⬜ Continuous Delivery ⬜ Infrastructure as Code
- 122. 131 @phermens The “100 to 1,000” checklist Responsibility ⬜ Can I control my deployments? ⬜ Have I removed all bottlenecks? ⬜ Do I have good support systems? ⬜ Am I collaborating with my peers? Autonomy ⬜ Freedom to innovate/improve? ⬜ Am I in control and independent? ⬜ Can I find out what went wrong? ⬜ Do I have the skills to fix it? Ownership ⬜ Agreed interfaces (or contracts?) ⬜ Out-of-the-box solutions? ⬜ Tooling is 100% automated? ⬜ Local build == “Production” build? Failure ⬜ Monitoring = Alerting = Action ⬜ Take pride in improving ⬜ Small deliverables, quickly ⬜ Non-blocking deployments
- 123. Questions?
- 124. Checklists!
- 125. 134 @phermens The “faster to master” checklist Developing ⬜ Coding guidelines ⬜ Code reviews ⬜ Code analysis ⬜ Short-lived branches ⬜ Feature toggles Monitoring ⬜ Defined key metrics ⬜ Measure – create dashboards ⬜ Proactivity – add alerting (& act!) Testing ⬜ Unit tests ⬜ Module tests ⬜ Integration tests ⬜ End-to-end tests ⬜ Test automation Deploying ⬜ Continuous Integration ⬜ Continuous Delivery ⬜ Infrastructure as Code
- 126. 135 @phermens The “100 to 1,000” checklist Responsibility ⬜ Can I control my deployments? ⬜ Have I removed all bottlenecks? ⬜ Do I have good support systems? ⬜ Am I collaborating with my peers? Autonomy ⬜ Freedom to innovate/improve? ⬜ Am I in control and independent? ⬜ Can I find out what went wrong? ⬜ Do I have the skills to fix it? Ownership ⬜ Agreed interfaces or contracts? ⬜ Out-of-the-box solutions? ⬜ Tooling is 100% automated? ⬜ Local build == “Production” build? Failure ⬜ Monitoring = Alerting = Action ⬜ Take pride in improving ⬜ Small deliverables, quickly ⬜ Non-blocking deployments