Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Javaone - From serverless to Service Full

2,083 views

Published on

How the role of devops is evolving

Published in: Technology
  • Be the first to comment

Javaone - From serverless to Service Full

  1. 1. From Serverless to ServiceFull How the mindset of devops is evolving @patrickdebois
  2. 2. Things I did (I’m proud of)
  3. 3. patrick@zender.tv http://zender.tv
  4. 4. Team of 7 people How do we do it ?
  5. 5. “Backend” services ELB
  6. 6. “Community” services
  7. 7. “IT support” services
  8. 8. Our “Office” services
  9. 9. “Frontend” services
  10. 10. “Mobile” services SNS/Push Cognito
  11. 11. Services #servicefull
  12. 12. https://asoldatenko.com/building-serverless-applications-with-python-3.html First time Ken Fromm in 2012 use this term in his article. “Serverless is delegating hardware or infrastructure to third parties or vendors. “
  13. 13. https://martinfowler.com/articles/serverless.html
  14. 14. A bit further down the rabbit hole …
  15. 15. limits not clear under stress
  16. 16. https://read.acloud.guru/does-coding-language-memory-or-package-size-affect-cold-starts-of-aws-lambda-a15e26d12c76
  17. 17. container re-use non-deterministic
  18. 18. Github
  19. 19. limits and unavailable
  20. 20. service got disabled because of too many bounces
  21. 21. autoscaling is too slow for peak traffic
  22. 22. inconsistent behaviour
  23. 23. (almost) NO MAINTENANCE
  24. 24. increased risk when not available
  25. 25. You are an Agent
  26. 26. You make promises to others in the system
  27. 27. Your promises should be verifiable
  28. 28. A promise does not guarantee an outcome
  29. 29. Conditions should be part of your promise
  30. 30. It needs to be clearly documented otherwise it’s not a promise
  31. 31. the language of a promise must be shared
  32. 32. It needs to be mutually agreed (not obligation) otherwise it’s not a promise
  33. 33. You might depend on other agents to keep your promises
  34. 34. Other agents make promises to you
  35. 35. Their promises need to be verifiable clearly documented & mutually agreed (not obligation)
  36. 36. But you can not make promises on behalf of other agents (bottom up vs top down)
  37. 37. Promises can be conflicting in a system
  38. 38. but the conflict can only be from internal promises (as we can not be responsible for others promises)
  39. 39. To keep a promise you should have a choice
  40. 40. Agents with a similar goal can be grouped into a Super Agent
  41. 41. Single Leaves = SPOF You need multiple Super Agents to have a choice again
  42. 42. Services
  43. 43. Single Leaves = SPOF To create choice you need to eliminate the single leaves (SPOF)
  44. 44. http://openwhisk.incubator.apache.org/
  45. 45. Forksv1 v2 v3 v1 v2 v3 To keep promises agent can introduce different world views (versions)
  46. 46. Slows down A super agent might get slow internal communication speed is key
  47. 47. Scaling Promises keeping your promise while changing your size (is hard)
  48. 48. Every promise binding is the basis for relationship (Dunbar)
  49. 49. services devops
  50. 50. Holy Cow!
  51. 51. “I introduced devops and all I got was a remote API”
  52. 52. “As the geeks would say, given enough apps, all of humanity’s bugs are shallow” Evgeny Morozov
  53. 53. It’s devops Jim but not as we know it
  54. 54. emerging practices
  55. 55. communicate the status of your promise and monitor others
  56. 56. monitor your services and expose your own metrics (API)
  57. 57. expose insights to other agents (API)
  58. 58. show that you care about other agents
  59. 59. expose your logs
  60. 60. be clear on what happens when it fails
  61. 61. backup external data (give an API please)
  62. 62. provide & seek fast feedback on your promise change status
  63. 63. be clear on your dependencies and expect the same of other services
  64. 64. be proactive to make others keep their promises
  65. 65. give insights on changing promises
  66. 66. talk at conferences to indicate your willingness to share
  67. 67. make it convenient for other agents to use
  68. 68. let other agents influence your changing promises
  69. 69. show that you listen to those that depend on you
  70. 70. show that your participation by improving the field
  71. 71. be responsive to requests
  72. 72. provide feedback to other agents
  73. 73. show that your engineers are not afraid of talking to people
  74. 74. External Services are the next silo
  75. 75. “The collaboration between dev & ops is now extended to external 3rd parties”
  76. 76. “make clear promises to other agents”
  77. 77. “And verify the status of other agents promises”
  78. 78. “To keep your promise to the business”
  79. 79. To be an engineer … is not enough to be an engineer” José Ortega y Gasset
  80. 80. https://github.com/anaibol/awesome-serverless

×