DevOps: 2009 to 2019 - 2019-09-25

99d4c0ed3c8027ea1c37b53d6441d042?s=47 sullis
September 25, 2019

DevOps: 2009 to 2019 - 2019-09-25

Portland DevOps meetup
Portland Oregon
September 25, 2019

#devops
#pdxtech

99d4c0ed3c8027ea1c37b53d6441d042?s=128

sullis

September 25, 2019
Tweet

Transcript

  1. 5.
  2. 6.
  3. 7.
  4. 10.
  5. 11.
  6. 12.
  7. 13.
  8. 14.
  9. 15.
  10. 16.
  11. 17.
  12. 19.
  13. 20.
  14. 21.
  15. 22.
  16. 23.
  17. 24.
  18. 25.
  19. 26.
  20. 27.
  21. 28.
  22. 29.
  23. 30.
  24. 32.
  25. 33.
  26. 36.

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

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

    “a deployment pipeline is an automated manifestation of your process

    for getting software from version control into the hands of your users”
  28. 38.
  29. 39.
  30. 40.

    “The findings from our research show clearly that the value

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

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

    Mean Time to Restore (MTTR) 4. Change Fail Percentage
  32. 43.
  33. 44.
  34. 46.

    “A key part of DevOps for the database is to

    recognize that this schema is code”
  35. 47.

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

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

    “you need to be able to upgrade the database schema

    without breaking the application”
  37. 49.

    “you also need to be able to upgrade the application

    and run it against an old schema version”
  38. 51.
  39. 53.

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

    Frequency 3. Mean Time to Restore (MTTR) 4. Change Fail Percentage 5. Availability
  40. 56.
  41. 58.