Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Cloud Foundry Summit 2015: Devops, microservices and platforms, oh my!

4.108 Aufrufe

Veröffentlicht am

Speaker: Andrew Clay Shafer

To learn more about Pivotal Cloud Foundry, visit pivotal.io/platform-as-a-serivce/pivotal-cloud-foundry

Veröffentlicht in: Technologie
  • Als Erste(r) kommentieren

Cloud Foundry Summit 2015: Devops, microservices and platforms, oh my!

  1. 1. devops, microservices and platforms, oh my! Andrew Clay Shafer Senior Director of Techology
  2. 2. systems thinking is the new black
  3. 3. a stone cutter’s quest for nice things
  4. 4. Andrew Clay Shafer
  5. 5. Andrew Clay Shafer @littleidea
  6. 6. Three Stone Cutters walk into a Pareto Inefficient Nash Equilibrium
  7. 7. start with the conclusion
  8. 8. devops, platforms, continuous delivery, microservices…
  9. 9. These things are all one…
  10. 10. In the beginning…
  11. 11. not the beginning beginning
  12. 12. I got a job as a developer…
  13. 13. I was smart…
  14. 14. I had no idea what I was doing…
  15. 15. I was left to my own devices…
  16. 16. • no experience • no mentors • no testing • no backups • no version control • no automation ¯_(ツ)_/¯
  17. 17. a boy, a server and force of will
  18. 18. it mostly worked
  19. 19. next stop… grad school
  20. 20. Computational Science • model bioelectric fields • solve for measurements • visualize • rinse and repeat
  21. 21. learned a few things • technical debt • Conway’s Law • subversion • little to no testing
  22. 22. Venture Funded Solutions in search of problems
  23. 23. Linux ‘server’ in your Pocket • custom board • 400 MHz PowerPC • 64 MB SDR SDRAM • 512 MB NAND FLASH • USB Powered • biometric auth
  24. 24. Big Vision • Identity Solution • Policy Based Provisioning • Citrix Desktop • On demand ‘deb’ package • Poison Pill • Mostly Worked
  25. 25. Learned More Things • Formative • Learned to Computer • Introduced to Agile™ • Testing • Project Management • Lord Conway Reigns • Disassociated Identity
  26. 26. The next chapter • eCommerce 2.0 • J2EE • DIY Square Wheels • Outsourced Ops • Brittle • Expensive
  27. 27. very clever solutions
  28. 28. Automation… • write a script for common tasks • share the scripts around office • modify the scripts for new task • hope things works
  29. 29. Typical Day at Work
  30. 30. the mission begins
  31. 31. to change the relationship between people and computers
  32. 32. actually, needed to change the relationship between people and people
  33. 33. Velocity 2009
  34. 34. Amazon, a bookstore in Seattle, deploys code to production every 11 seconds…
  35. 35. –Werner Vogels, CTO Amazon “The traditional model is that you take your software to the wall that separates development and operations, and throw it over and then forget about it. Not at Amazon. You build it, you run it. This brings developers into contact with the day-to-day operation of their software. It also brings them into day-to-day contact with the customer. This customer feedback loop is essential for improving the quality of the service.”
  36. 36. everybody looks at Amazon and rushes to copy features
  37. 37. but the features are superficial the Amazon advantage is the process and culture
  38. 38. Operations is the secret sauce configuration
  39. 39. Day 2 matters
  40. 40. Principles > Practices >Tools
  41. 41. let’s rewind that
  42. 42. Software in the beginning • shipped on physical media • hard to change after release • runs on other peoples computers • have to worry about bugs • process doesn’t run very long • no worries about uptime
  43. 43. Software Developer changes ideas into code
  44. 44. The Process • have a good idea! • request a server • get a purchase order from supervisor • wait • wait • server arrives • server gets power and network • server gets operating system • start to configure for deploy Traditional IT
  45. 45. The System Admin • keeps systems running • don’t care about your application • not paid to care • other people waiting for their servers • might have to worry about many other servers • and email • and printers
  46. 46. The shift to services • the internet changes everything • runs on other your computers • can change your computers • still have to worry about bugs • process run a long time • uptime is everything
  47. 47. bigger, faster, stronger
  48. 48. But we are an enterprise, we are different, we cannot do this, we have our ways.
  49. 49. service management? ITIL
  50. 50. seemed like a good idea slow everything down
  51. 51. Is moving slow an advantage?
  52. 52. dev ops
  53. 53. are misaligned incentives an advantage?
  54. 54. not how the web was built competitive disadvantage
  55. 55. The Stories We Tell
  56. 56. configuration management for the masses
  57. 57. The Process • have a good idea! • request a server • get a server in minutes • run configuration tools • everything is up in minutes
  58. 58. Principles > Practices >Tools
  59. 59. Adrian Cockroft - ex-Netflix What I learned from my time at Netflix.
  60. 60. Netflix Lessons • Speed wins in the marketplace • Remove friction from product development • High trust, low process, no hand-offs between teams • Freedom and responsibility culture • Don’t do your own undifferentiated heavy lifting • use simple patterns automated by tooling • self service cloud makes impossible things instant
  61. 61. But we are an enterprise, we do not have the talent to do this. “But Netflix has a superstar development team, we don’t”
  62. 62. “Netflix hired them from you, and got out of their way.”
  63. 63. Time Risk the impact of batch size
  64. 64. both faster and safer
  65. 65. –W Edwards Deming “It is not necessary to change. Survival is not mandatory.”
  66. 66. Netflix built a platform to enable self service deployment
  67. 67. Netflix built a platform to deploy and operate microservices
  68. 68. Netflix built a platform to continuously deliver software
  69. 69. Netflix built a platform that could protect itself from failure
  70. 70. What Netflix did not do is build a platform for general ad-hoc automation…
  71. 71. A platform makes promises. Constraints are the contract that allows the platform to keep promises.
  72. 72. Principles > Practices >Tools
  73. 73. devops refers to the practices and tools that emerge from high performing organizations
  74. 74. continuous delivery results as a consequence of devops practice
  75. 75. continuous delivery is not possible with gating and handoffs
  76. 76. continuous delivery is untenable, if the fixed cost of deployment is high
  77. 77. microservices describes the first post-cloud, post-devops, post- continuous delivery architecture
  78. 78. microservices leverage baseline operational capabilities and team dynamics to isolate failure and maximize velocity
  79. 79. continuously delivered microservices are the natural evolution for services that need to run at scale and be changed frequently
  80. 80. Amazon, Google, Netflix, Flickr, Etsy, WealthFront, Lyft, Uber, Shopzilla, Pied Piper, all built one off platforms to do this
  81. 81. continous delivery - why devops - how microservices - what
  82. 82. the solution: a platform
  83. 83. Do you want to build one?
  84. 84. maybe we can build one together
  85. 85. The Process • have a good idea! • push code to platform • code is running in seconds • self service • self healing • and they all lived happily ever after
  86. 86. no one originally set out to do devops, continuous delivery, microservices, or platforms these were natural consequences don’t fixate on the words, fixate on the outcomes
  87. 87. This is not the end…
  88. 88. mobile, internet of things, big data everything is getting bigger and faster

×