Download to read offline
![106
@phermens
[REDACTED]
[REDACTED]](https://image.slidesharecdn.com/from100to1000deploymentsadaycodemotion-190519124344/75/Pat-Hermens-From-100-to-1-000-deployments-a-day-Codemotion-Amsterdam-2019-98-2048.jpg)
Uploaded byCodemotion
Pat Hermens - From 100 to 1,000+ deployments a day - Codemotion Amsterdam 2019
The document presents a discussion led by Pat Hermens on achieving over 1,000 deployments per day, sharing insights from his experience in development and deployment practices. It outlines a 'faster to master' checklist that emphasizes the importance of coding guidelines, testing, continuous integration, and monitoring for successful deployments. The presentation also touches on themes of responsibility, autonomy, and ownership within DevOps teams.
More Related Content
Similar to Pat Hermens - From 100 to 1,000+ deployments a day - Codemotion Amsterdam 2019
Pat Hermens - From 100 to 1,000+ deployments a day - Codemotion Amsterdam 2019
- 1. From 100 to1000+ deployments a day Pat Hermens Amsterdam | April 2-3, 2019
- 2. From 100 to1,000+ deployments What does it take to get to the next level?
- 3. Pat Hermens Development Manager Codingfor 15+ years Father & husband Rotterdam, Netherlands @phermens pat@coolblue.nl
- 5.
- 6.
- 7.
- 15. 100 / 1,000/ 10,000; so what?
- 16.
- 17. … Apparently weare 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.
- 21. 23 @phermens The “faster tomaster” 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.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44. 49 @phermens Serilog + Splunk+ DataDog
- 50.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65.
- 66.
- 67.
- 68.
- 69.
- 70.
- 71. 77 @phermens AWS Lambda statsfor Vanessa Optima Prime (as of 2019-04-01) Last 30 days Last 7 days
- 72. 78 @phermens AWS Lambda statsfor Vanessa Optima Prime (as of 2019-04-01) Last 30 days Last 7 days
- 73.
- 74.
- 75.
- 76.
- 77.
- 78.
- 79.
- 80.
- 81.
- 82.
- 83.
- 84.
- 85.
- 86.
- 87.
- 88.
- 89.
- 90. 96 @phermens Fail early, failoften, but always fail forward.
- 91.
- 98.
- 100.
- 102.
- 104.
- 107.
- 112.
- 115.
- 116.
- 118.
- 119.
- 120.
- 121. 130 @phermens The “faster tomaster” 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 to1,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.
- 124.
- 125. 134 @phermens The “faster tomaster” 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 to1,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
- 127.
- 128.