DevOps: 2009 to 2019 - 2019-09-25

Transcript

1. 1.

   DevOps 2009 to 2019 Sean Sullivan Portland DevOps meetup September

   25, 2019
2. 2.

   About me: Scala Java Kotlin Python

3. 3.

   deleted scenes

4. 4.

   Linux could be most aptly described as agrarian pre-capitalist

5. 5.

   Ubuntu

6. 6.

   Dev Ops

7. 7.

   YAML

8. 8.

   YAML Docker

9. 9.

   DevOps YAML Docker Kubernetes

10. 10.

    Twitter

11. 11.

    None
12. 12.

    None
13. 13.

    None
14. 14.

    None
15. 15.

    June 2009

16. 16.

    None
17. 17.

    None
18. 18.

    Paul Hammond John Allspaw

19. 19.

    None
20. 20.

    None
21. 21.

    None
22. 22.

    None
23. 23.

    None
24. 24.

    None
25. 25.

    None
26. 26.

    None
27. 27.

    None
28. 28.

    None
29. 29.

    None
30. 30.

    None
31. 31.

    Flickr could be most aptly described as agrarian pre-DevOps

32. 32.

    2010

33. 33.

    None
34. 34.

    “Create a repeatable, reliable process for releasing software”

35. 35.

    “If it hurts, do it more frequently, and bring the

    pain forward.”
36. 36.

    “If releasing software is painful, aim to release it every

    time somebody checks in a change that passes all the automated tests.”
37. 37.

    “a deployment pipeline is an automated manifestation of your process

    for getting software from version control into the hands of your users”
38. 38.

    2018

39. 39.

    None
40. 40.

    “The findings from our research show clearly that the value

    of adopting DevOps is even larger than we had initially thought”
41. 41.

    “the gap between high and low performers continues to grow”

42. 42.

    Software delivery performance: 1. Lead Time 2. Deployment Frequency 3.

    Mean Time to Restore (MTTR) 4. Change Fail Percentage
43. 43.

    2019

44. 44.

    None
45. 45.

    “Most companies don’t include their databases in their DevOps practices”

46. 46.

    “A key part of DevOps for the database is to

    recognize that this schema is code”
47. 47.

    “[the database schema] should be stored in source control, and

    subject to the same processes and controls as application source code”
48. 48.

    “you need to be able to upgrade the database schema

    without breaking the application”
49. 49.

    “you also need to be able to upgrade the application

    and run it against an old schema version”
50. 50.

    Postgres could be most aptly described as agrarian NoSQL

51. 51.

    None
52. 52.

    “speed and stability are both possible”

53. 53.

    Software delivery and operational performance: 1. Lead Time 2. Deployment

    Frequency 3. Mean Time to Restore (MTTR) 4. Change Fail Percentage 5. Availability
54. 54.

    Elite performers: 208 times more frequent code deployments 2604 times

    faster time to recover from incidents
55. 55.

    DevOps could be most aptly described as decentralized cat herding

56. 56.

    DevOps

57. 57.

    Thank you! tinyrobots

58. 58.

    DevOps