Months to Minutes - Real world continuous Deployment

Let’s be honest: How often do you release software and how much do you like it? In this talk, I’m going to share how we transformed our development process from half-year releases to multiple deployments per day. I’ll give an overview about the real world challenges we faced, the processes that turned out to be game changers for us and how the overhaul of delivery increased our productivity and product quality.

What you’ll learn:

– Overcoming the hurdles of traditional release cycles
– Why releasing multiple times a day is in fact less risky than traditional software deployment
– Shifting team culture to embrace rapid, reliable releases
– How communication and not tech was one of the main challenges to overcome

Transcript

1. Months to Minutes Real world continuous Deployment and it's sustainability impact
2. Who‘s that guy? Seeking fresh minds to share the kudos... and the occasional “technical oopsies”! MOIKO Card Solutions
3. So, what‘s the topic for today?
4. My confession:
5. Beginning of a Start-Up
6. After a while…
7. Different perception of „Feedback“
8. Solution(?): Longer release cycles
9. Alternatives to status quo?
10. Timeboxing („Sprint cycles“)
11. CI / CD
12. Value stream mapping https://project-management.com/value-stream-mapping-tools-software/
13. Integrate daily
14. Automation, Automation, Automation • Code-review (AI-driven?) • Builds • Feature branch environments • Tests • Code scanning • Security scans • Deployments • …
15. Make it easy to go back!
16. Can we fix this today?
17. What about green it?
18. What about green it?
19. What about green it?
20. What about green it?
21. What about green it?
22. Automation impact • Dev-Environment shuts down at night • „rightsizing“ through scaling • Faster builds = less energy consumption
23. Efficient human resources • Shorter feedback cycles • Less wasted work • Less coffee and pizza consumption • Less teams calls • Less CO2 Emissions from yelling managers • Less thrown keyboards
24. So long, and thanks for All the fish!
25. Dev cluster • Standard_D4s_v4 (1-2 instances) ~100w • Standard_D4s_v5 (1-2 instances) ~100w • Standard_D8ls_v5(1-3 instances) ~200w • Standard_D4ls_v5(1-3 instances) ~100w  Minimum of 237,5 g / hour  Maximum of 617,5 g / hour 12h offline = 2,85 kg min / 7,41 kg max Ca. 40-50km Flight daily / 10.000km per year Yearly power consumption 1 household (depending on energy sources) https://azure.microsoft.com/en-us/explore/global-infrastructure/sustainability
26. Useless code • 30-50% of code might never be executed or redundant (O‘Reilly Media) • Software carbon intensity (SCI) to quantify emissions (by Green Software foundation) • Save 50% of our useless or inefficient code, we save 15-25% of overall IT Emissions
27. CO2-Emissions of a Pizza https://maxhalford.github.io/blog/carbon-footprint-pizzas/
28. CO2-Emissions of a cup of coffee https://www.co2everything.com/co2e- of/coffee#:~:text=One%20cup%20of%20Coffee%20(15g)%20is%20equivalent%20to%200.4kg,equivalent%20to%200.4kg%20CO2e.
29. Saved Teams call https://www.cursor.tue.nl/en/news/2021/december/week-3/your-teams-meeting-has-a-larger-footprint-than-you-think/