Next Level: DevOps

Next Level: DevOps

Gave this talk at Take Off Conference in Lille, France on January 30th, 2014
Follow me on Twitter: @CodeStars

My current company hired me as a Software Engineer. Their software has organically grown over the past six years and it really looks like what you would expect, when you hear that a software system is that old. There was no real abstraction, no idea of services - nothing fancy.
I realized that if I wanted to change the software I had to start with the system architecture. Thus, I joined the infrastructure team where I learned a lot of new stuff as well as what it meant to be on call.

4c50caee0c6a446a0b60f827a2a1e5e5?s=128

Ole Michaelis

January 30, 2014
Tweet

Transcript

  1. NEXT LEVEL: DEVOPS Take Off Conference - January 30th -

    Lille, France
  2. @CodeStars! github.com/nesQuick! codestars.eu! ! So Coded Conference! slidr.io OLE MICHAELIS

  3. ANYWAY! WHAT ABOUT YOU?

  4. MY DEVOPS STORY

  5. 
 “Open Source Rockstar”! aka! WORKING @JIMDO

  6. None
  7. None
  8. None
  9. None
  10. LET’S TRY TO DEFINE DEVOPS

  11. YOU BUILD IT, YOU RUN IT! “The DevOps prime directive”

  12. ANTI-PATTERNS “You are doing it wrong!” NO! BECAUSE NO http://i.huffpost.com/gen/1143905/original.jpg

  13. ANTI-ANTI-PATTERNS “Ahhh... better!”

  14. None
  15. BECOME A DEVOPS

  16. EXTEND YOUR DEV SKILLS

  17. GATHER OPS KNOWLEDGE

  18. KNOW YOUR ENEMY!

  19. 0 25 50 75 100 Main memort ref

  20. 0 1000000 2000000 3000000 4000000 Main memort ref Disk Seek

  21. 0 40000000 80000000 120000000 160000000 Main memort ref Disk Seek

    Package Roundtrip
  22. None
  23. THE DEVOPS TOOLBOX

  24. * AS A SERVICE

  25. DEPLOYMENT

  26. None
  27. CONTINUOUS DELIVERY Ship when it’s done!

  28. CONTINUOUS DEPLOYMENT Shipin’ all the time!

  29. PULL DEPLOY Stop pushing, start pulling!

  30. STRATEGIES

  31. ONE, SOME, MANY

  32. ONE, SOME, MANY

  33. ONE, SOME, MANY

  34. ONE, SOME, MANY

  35. BLUE / GREEN

  36. METRICS

  37. SYSTEM VS. APPLICATION

  38. WHAT TO MEASURE?

  39. WHAT TO MEASURE? requests

  40. WHAT TO MEASURE? requests querys

  41. WHAT TO MEASURE? requests querys exceptions

  42. WHAT TO MEASURE? requests querys exceptions logs

  43. WHAT TO MEASURE? requests querys exceptions logs connections

  44. WHAT TO MEASURE? requests querys exceptions logs connections user

  45. WHAT TO MEASURE?

  46. None
  47. MEASURE WHATEVER MAKES FUCKING SENSE!

  48. None
  49. None
  50. FAILURE IS GOOD

  51. BE OPEN

  52. BE OPEN

  53. BE AGILE

  54. STAY HUNGRY

  55. IT’S ALL ABOUT MINDSET!

  56. THANK YOU! @CodeStars

  57. intentionally left blank slide

  58. http://martinfowler.com/bliki/BlueGreenDeployment.html! http://nikic.github.io/2011/12/27/Dont-be-STUPID-GRASP-SOLID.html! http://en.wikipedia.org/wiki/SOLID_(object-oriented_design)! http://www.shutterstock.com! http://icomoon.io/app/! http://apievangelist.com/2012/01/12/the-secret-to-amazons-success-internal-apis/! http://en.wikipedia.org/wiki/Structural_pattern! http://en.wikipedia.org/wiki/Creational_pattern! http://en.wikipedia.org/wiki/Behavioral_pattern! http://www.eecs.berkeley.edu/~rcs/research/interactive_latency.html!

    http://bfwa.com/pitfalls/! http://farm9.staticflickr.com/8491/8344781525_5787255ec2_z.jpg! http://docs.hostedgraphite.com/_images/sample_dashboard_conc_users_advanced.png! http://oss.oetiker.ch/rrdtool/gallery/btdmd8.png! http://www.wadsam.com/wp-content/uploads/2012/11/stock-exchagne.jpeg! http://s3.amazonaws.com/crunchbase_prod_assets/assets/images/original/0018/2843/182843v2.png! http://2.bp.blogspot.com/-t2FW5rx_yn0/TxVwhmqAXgI/AAAAAAAAA7s/DSdFmMZ5ecM/s1600/trading-floor.jpg! http://en.wikipedia.org/wiki/Mutual_exclusion! ! Thanks to all the people helped me so much! Elena ! Ingo! Nils! Nadja! Fridel! Spring! Mathias! Jimdo! Sources:
  59. AND ALWAYS REMEMBER: SAYS ␠