The first decade of DevOps is over!

In the beginning DevOps was an experiment to improve the collaboration just between Dev and Ops people. Today DevOps is often seen as tooling, as many tremendous changes in IT happened since then: the rise of container technology, Microservices, Public Cloud Services, Serverless and Infrastructure as Code - just to name a few of them. But DevOps is much more than technology and tooling. Books like ‚The Phoenix Project‘ were an eye opener to the process and people aspects of DevOps. A big set of different collaboration models between Dev and Ops like SRE have been developed. We learned about topics like Continuous Delivery, Observability, ChatOps etc. and how more departments than Dev and Ops will be affected by this new way of delivering digital products. The talk will end up giving an outlook to the next exciting decade of DevOps …

Transcript

1. The first decade of DevOps is over! Konstantin Diener | cosee GmbH konstantin.diener@cosee.biz | @onkelkodi
2. KONSTANTIN DIENER CTO and founder of cosee
3. Discovery- Phase Backlog Expert-Teams Billing Models Iterative Delivery So ware- Releases
6. https://de.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr/
7. https://de.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr/
8. https://de.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr/ Ops’ job is to enable the business (this is dev’s job too)
10. What was 2009 like?
12. Ops: Provisioning of Software, Servers & Networks
13. On-Premise Hosting
14. Infrastructure is an INVESTMENT
15. AWS is 3 years old
16. Agile Manifesto is 8 years old
17. Agile Delivery
22. Technology
23. smaller deployment units
24. 2009 2019
25. Containers
26. Public Cloud & Managed Services
27. Servers, Networks etc. Infrastructure as a Service Managed Service Infrastructure as a Service Infrastructure as a Service Managed Service Managed Service Managed Service Managed Service Application
28. 2009 2019
30. Infrastructure as Code
31. Cattle vs. Pet
32. 2009 2020 965-01-node-vs-test irene
33. Infrastructure as Code is important
34. But … ☝
35. • #1 Normalize the technology stack • #2 Standardize and reduce variability • #3 Expand DevOps practices • #4 Automate infrastructure delivery • #5 Provide self-service capabilities 2018 State of DevOps Report
36. But DevOps isn’t just IaC
37. DevOps is collaboration
38. Werner Vogels, Amazon “You build it, you run it”
39. Observability
40. New collaboration models
41. @noidi „Having a dedicated DevOps person who does all the DevOpsing is like having a dedicated collaboration person who does all the collaborating.“
42. Embedding Ops as a Service Collaboration Inspired by devopstopologies.com
43. devopstopologies.com
44. Site Reliability Engineering
45. Site Reliability Engineering or Ops done by Software Engineers
46. Failure & Transparency
47. Werner Vogels, Amazon “Everything fails all the time”
48. Chaos Engineering
49. Blameless Postmortems
50. Sharing is caring
51. https://blog.github.com/2018-10-30-oct21-post-incident-analysis/
52. ChatOps Jason Hand
53. Outlook
54. Is operating servers your core business?
55. Servers, Networks etc. Infrastructure as a Service Managed Service Infrastructure as a Service Infrastructure as a Service Managed Service Managed Service Managed Service Managed Service Application
56. • Keep your proprietary code and infrastructure as minimal as possible. • Try to automate everything. • Avoid pet infrastructure.
58. • Learn from failure! • Share your learnings (company + customers + community)! • Choose a setup for real collaboration. • Build real cross-functional teams (together with business, support, marketing, …)!
59. But …
60. Homework 2030: tackle complexity
61. konstantin.diener@cosee.biz | @onkelkodi Let’s keep in touch! Konstantin Diener | cosee GmbH cosee.biz Picture credits: Gated Bridge: https://www.istockphoto.com/de/portfolio/vesilvio Dog:https://www.istockphoto.com/de/portfolio/sestovic Cows:https://www.istockphoto.com/de/portfolio/pixinoo