Download to read offline
More Related Content
Similar to Subverting the monolith!
Subverting the monolith!
- 1. Subverting the Monolith With Principlesand Tooling @girlnamedsophia
- 2. We’ve been toldthe future is… Automated Serverless In the cloud Distributed Scalable Flexible Resilient Secure
- 4. How do yougo from here to there? Here There
- 5.
- 6.
- 7. • Apps aren’t12 factor …where were we?
- 8. • Apps aren’t12 factor • Not all hosts are ephemeral …where were we?
- 9. • Apps aren’t12 factor • Not all hosts are ephemeral • High deploy latency - 90 minute deploys …where were we?
- 10. • Apps aren’t12 factor • Not all hosts are ephemeral • High deploy latency - 90 minute deploys • Low reliability in CI/CD …where were we?
- 11. • Apps aren’t12 factor • Not all hosts are ephemeral • High deploy latency - 90 minute deploys • Low reliability in CI/CD • High onboarding cost for new apps …where were we?
- 12. • Apps aren’t12 factor • Not all hosts are ephemeral • High deploy latency - 90 minute deploys • Low reliability in CI/CD • High onboarding cost for new apps …where were we?
- 13. • Apps aren’t12 factor • Not all hosts are ephemeral • High deploy latency - 90 minute deploys • Low reliability in CI/CD • High onboarding cost for new apps …where were we?
- 14.
- 15. • Code inVCS • Dependencies declared and isolated • Config stored in the environment • Backing services communicated over an API • Internal Services available via an API • Concurrency and scaling through the process model • Ephemeral • Environment agnostic • Logs as event stream • Admin tasks in production
- 16. So what is“there”? There
- 17. Serverless! Containerized! Environment Agnostic! Declarative Dependencies! Backingservices communicated over an API!
- 18.
- 19. Consumer Contract CI pipeline CDpipeline Onboard new apps
- 20. And when dowe want it?
- 21.
- 22. How do wewant it to happen?
- 23.
- 24. Why don’t wehave it already?
- 26. How we builtthe platform today, thinking of tomorrow Solved one problem at a time
- 27. Solved one problemat a time Implemented Configuration as Code How we built the platform today, thinking of tomorrow
- 28. Solved one problemat a time Implemented Configuration as Code Prioritized an engineers-first approach How we built the platform today, thinking of tomorrow
- 29. Solved one problemat a time Implemented Configuration as Code Prioritized an engineers-first approach How we built the platform today, thinking of tomorrow …okay, engineers second, Principles first
- 30.
- 31. Which problem tosolve first?
- 32. Consumer Contract CI Pipeline CDPipeline Onboard new apps
- 33.
- 34.
- 35. Generic solution Varying needs UsableValue right off the bat
- 36. GitHub Jenkins GitHubJenkins Slack AWS JenkinsJenkinsJenkinsJenkins Sad engineers shake fists CI/CD not in VCS Onboarding new apps is difficult Sad Engineer CI fumbles Not Atomic!
- 37. GitHub Jenkins GitHubJenkins Slack AWS JenkinsJenkinsJenkinsJenkins Sad Engineer CI fumbles
- 38.
- 39.
- 40.
- 41. As engineers, what’syour go to language of choice? What do you write most of your tools things in? 1. Ruby 2. Elixir 3. Golang
- 42.
- 43. So what didwe do? We wrote YAML… WITH RUBY
- 44. Enforces a setof conventions What’s the tool do?
- 45. What’s the tooldo? Enforces a set of conventions Defines a predetermined contract
- 46. Enforces a setof conventions Defines a predetermined contract Automates configuration generation What’s the tool do?
- 47. Why did wedo it?
- 48. Externalized Configuration Why acontract?
- 49.
- 50.
- 51. Why a contract? ExternalizedConfiguration Automation Scalability Standardization
- 52. Why a contract? ExternalizedConfiguration Automation Scalability Standardization Predictability
- 53. Why a contract? ExternalizedConfiguration Automation Scalability Standardization Predictability
- 54. Why a contract? ExternalizedConfiguration Automation Scalability Standardization Predictability
- 55. RSpec Rubocop Integration Tests Error Screenshots StandardizedBuilds Conventionally stored artifacts
- 56.
- 57. How’s it work? ruby_appjava_appjava_library … Coach CLI
- 58.
- 59. How’s it work? ruby_app ruby_library java_library ruby2.6.1 ruby 2.4.2 java 1.8.0
- 60.
- 61.
- 63. Consumer Contract CI Pipeline CDPipeline Onboard new apps
- 64.
- 65.
- 66.
- 67.
- 68.
- 69.
- 70.
- 74.
- 80.
- 81.
- 82.
- 83.
- 84.
- 85.
- 86.
- 87. …where are wenow?
- 88. …where are wenow? • Apps start to look a lot more 12 factor-y
- 89. …where are wenow? • Apps start to look a lot more 12 factor-y • Not all hosts are ephemeral
- 90. …where are wenow? • Apps start to look a lot more 12 factor-y • Not all hosts are ephemeral • Low deploy latency - 25-35 minute deploys
- 91. …where are wenow? • Apps start to look a lot more 12 factor-y • Not all hosts are ephemeral • Low deploy latency - 25-35 minute deploys • High reliability in CI, not yet CD
- 92. …where are wenow? • Apps start to look a lot more 12 factor-y • Not all hosts are ephemeral • Low deploy latency - 25-35 minute deploys • High reliability in CI/CD, not yet CD • Low onboarding cost for new apps
- 93. …where are wenow? • Apps start to look a lot more 12 factor-y • Not all hosts are ephemeral • Low deploy latency - 25-35 minute deploys • High reliability in CI/CD, not yet CD • Low onboarding cost for new apps
- 94. …where are wenow? • Apps start to look a lot more 12 factor-y • Not all hosts are ephemeral • Low deploy latency - 25-35 minute deploys • High reliability in CI/CD, not yet CD • Low onboarding cost for new apps
- 95. How our toolingEncouraged Developers to Build for the Future
- 96. Consumer Contract CI Pipeline CDPipeline Onboard new apps
- 97. From legacy to newworld
- 98.
- 99.
- 100. An app isan app is an app
- 101.
- 102. What is butisn’t an app? • Database migrations for a shared database • Database monitoring that needs to run on its own host
- 103. Running the codein the cloud
- 104.
- 105.
- 106. What language ortool do you use to keep infrastructure in code? 1. YAML 2. Terraform 3. Ansible
- 107. Terraform with Ruby Helmwith Ruby
- 110. The evolution ofthe platform ruby_app database_ monitoring _app database_ migration_ app ruby_app_ database
- 111.
- 112. The engineers andthe principles guide the tools
- 113. Consumer Contract CI Pipeline CDPipeline Onboard new apps
- 114. Define the contract Enforcethe contract Onboard
- 115.
- 116.
- 117. Ease of distribution meansease of adoption
- 118. Did we subvertthe monolith?
- 119.
- 120. • Apps are12 factor! • All hosts are ephemeral, we can even support one-off ecosystems with ease • Low deploy latency - 10-25 minute deploys • High reliability in CI/CD • Low onboarding cost for new apps …where are we now?
- 121. GitHub Jenkins GitHubJenkins Slack AWS JenkinsJenkinsJenkinsJenkins Sad Engineer
- 122. GitHub CircleCI CoachWeb Slack Coach CLI GitHub Happy Engineer
- 123. GitHub CircleCI CoachWeb Slack Coach CLI GitHub Happy Engineer Jenkins AWS EKS Rudder
- 124.
- 126. Sometimes the solutioncan be well-designed and knowingly temporary
- 127. Automation now isbetter than manual later
- 128. Delivering value asquickly as possible without sacrificing quality is critical to growth
- 129. With clearly definedprinciples and goals, know that you never need to stop iterating
- 130. Our present is… Automated Serverless Inthe cloud Distributed Scalable Flexible Resilient Secure
- 131.
- 132.