$30 off During Our Annual Pro Sale. View Details »

The first decade of DevOps is over!

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 …

Konstantin Diener

November 27, 2019
Tweet

More Decks by Konstantin Diener

Other Decks in Technology

Transcript

  1. The first decade of DevOps is over!
    Konstantin Diener | cosee GmbH
    [email protected] | @onkelkodi

    View Slide

  2. KONSTANTIN DIENER
    CTO and founder of cosee

    View Slide

  3. Discovery-
    Phase
    Backlog
    Expert-Teams
    Billing
    Models
    Iterative
    Delivery
    So ware-
    Releases

    View Slide

  4. View Slide

  5. 2009

    View Slide

  6. https://de.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr/

    View Slide

  7. https://de.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr/

    View Slide

  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)

    View Slide

  9. View Slide

  10. What was 2009 like?

    View Slide

  11. View Slide

  12. Ops: Provisioning of Software,
    Servers & Networks

    View Slide

  13. On-Premise Hosting

    View Slide

  14. Infrastructure is an INVESTMENT

    View Slide

  15. AWS is 3 years old

    View Slide

  16. Agile Manifesto is 8 years old

    View Slide

  17. Agile Delivery

    View Slide

  18. View Slide

  19. View Slide

  20. View Slide

  21. 2020

    View Slide

  22. Technology

    View Slide

  23. smaller deployment units

    View Slide

  24. 2009 2019

    View Slide

  25. Containers

    View Slide

  26. Public Cloud &
    Managed Services

    View Slide

  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

    View Slide

  28. 2009 2019

    View Slide

  29. View Slide

  30. Infrastructure as Code

    View Slide

  31. Cattle vs. Pet

    View Slide

  32. 2009 2020
    965-01-node-vs-test
    irene

    View Slide

  33. Infrastructure as Code is important

    View Slide

  34. But … ☝

    View Slide

  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

    View Slide

  36. But DevOps isn’t just IaC

    View Slide

  37. DevOps is collaboration

    View Slide

  38. Werner Vogels, Amazon
    “You build it, you run it”

    View Slide

  39. Observability

    View Slide

  40. New collaboration models

    View Slide

  41. @noidi
    „Having a dedicated DevOps person who does all the
    DevOpsing is like having a dedicated collaboration
    person who does all the collaborating.“

    View Slide

  42. Embedding Ops as a Service Collaboration
    Inspired by devopstopologies.com

    View Slide

  43. devopstopologies.com

    View Slide

  44. Site Reliability
    Engineering

    View Slide

  45. Site Reliability Engineering
    or
    Ops done by Software Engineers

    View Slide

  46. Failure & Transparency

    View Slide

  47. Werner Vogels, Amazon
    “Everything fails all the time”

    View Slide

  48. Chaos Engineering

    View Slide

  49. Blameless Postmortems

    View Slide

  50. Sharing is caring

    View Slide

  51. https://blog.github.com/2018-10-30-oct21-post-incident-analysis/

    View Slide

  52. ChatOps
    Jason Hand

    View Slide

  53. Outlook

    View Slide

  54. Is operating servers your core
    business?

    View Slide

  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

    View Slide

  56. • Keep your proprietary code and infrastructure as
    minimal as possible.
    • Try to automate everything.
    • Avoid pet infrastructure.

    View Slide

  57. View Slide

  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, …)!

    View Slide

  59. But …

    View Slide

  60. Homework 2030:
    tackle complexity

    View Slide

  61. [email protected] | @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

    View Slide