The First Decade of DevOps is Over by Konstanin Diener

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 Soft 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 2019 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 Inspired by devopstopologies.com
43. Embedding Ops as a Service Inspired by devopstopologies.com
44. Embedding Ops as a Service Collaboration Inspired by devopstopologies.com
45. devopstopologies.com
46. Site Reliability Engineering
47. Site Reliability Engineering or Ops done by Software Engineers
48. Failure & Transparency
49. Werner Vogels, Amazon “Everything fails all the time”
50. Chaos Engineering
51. Blameless Postmortems
52. Sharing is caring
53. https://blog.github.com/2018-10-30-oct21-post-incident-analysis/
54. ChatOps Jason Hand
55. Outlook
56. Is operating servers your core business?
57. 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
58. • Keep your proprietary code and infrastructure as minimal as possible. • Try to automate everything. • Avoid pet infrastructure.
60. • 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, …)!
61. But …
62. Homework 2029: tackle complexity
63. 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