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.

Rethinking enterprise architecture for DevOps, Agile, and cloud native organizations

Current application theory says that all responsibility for software should be pushed down to the actual DevOps-style team writing, delivering, and running the software. This leaves the EA role in the dust, seemingly killing it off. In addition to this being disquieting to EAs out there who have steep mortgage payments and other expensive hobbies, it seems to drop out the original benefits of enterprise architecture, namely oversight of all IT-related activities to make sure things don’t go wrong (e.g., spending, poor tech choices, problematic integration, etc.) and that things, rather, go right.

As presented at the O'Reilly Software Architecture Conference in Berlin, November 2019.

  • Loggen Sie sich ein, um Kommentare anzuzeigen.

  • Gehören Sie zu den Ersten, denen das gefällt!

Rethinking enterprise architecture for DevOps, Agile, and cloud native organizations

  1. 1. Rethinking enterprise architecture for DevOps, agile, & cloud native organizations Nov, 2019 @cote 1
  2. 2. 2 @cote https://cote.io/books Free!
  3. 3. 3 First, what is “enterprise architecture?
  4. 4. 4
  5. 5. 5 Source: Enterprise Architecture as Strategy, Jeanne W. Ross, Peter Weill, David Robertson, 2006.
  6. 6. 6
  7. 7. 7 The problem
  8. 8. 8 If I’m doing 8 or 15 releases a week, how am I going to get through all those CABs?” Mark Ardito, HCSC, Aug 2016 “
  9. 9. 9 Using external change approval processes such as a change advisory board, as opposed to peer-based code review techniques, significantly impacts throughput while doing almost nothing to improve stability.” Jez Humble, 2014 “
  10. 10. 10
  11. 11. 13Sources: "Building a Brand Around a Technology and Cultural Transformation," Matt Curry, Sep. 2016.
  12. 12. 14 Leading change
  13. 13. 15 Mobile payments Mortgage application Mortgage approval Bill pay Transfers 🤓 🤓 Private or public IaaS 👩💼👔👨💼Culture, process, methodology, governance, compensation, etc. IT Leadership, EAs, etc. Platform Engineers Product teams Corporate strategy, revenue goals, mission, etc. 💼🤑🏭🏢 🏛 🌥 ☁ “The Business”
  14. 14. 16
  15. 15. Beyond 10 ways to make coffee: leadership’s role ● Create a culture of innovation, risk taking, and focusing on people (“users”) ● Give product teams autonomy, trust, and voice ● Establish trust by doing what you say, delegating, and celebrating failurelearning. ● Feedback loop: surveys (ENPS), silence, churn, results. ● Giving feedback: OKRs, praising process & stories, not just schedule 17More: creating a DevOps culture, whatever that means.
  16. 16. 18 Gardening teams
  17. 17. 19Source: "You can do better than the Spotify Model," Joakim Sundén, Oct 2017. Tech staff growth
  18. 18. 20 Sources: Morning Coffee, Sarah Butcher, 23 February 2016; "Jamie Dimon: JPMorgan Employs 30,000 Programmers," April 2014. J.P. Morgan CFO Marianne Lake said the US bank now employs 40,000 technologists. That's an increase of 10,000 in two years (in a 2013 investor letter, JPM said it employed 30,000 technologists). 18,000 of those 40,000 are developers, said Lake.” “
  19. 19. 21 "The risk with this model is that the architecture of a system gets messed up if nobody focuses on the integrity of the system as a whole.” -Scaling Agile @ Spotify, Henrik Kniberg & Anders Ivarsson Oct 2012
  20. 20. 22
  21. 21. Closer to a product organization… 23 Mobile payments Mortgage application Mortgage approval Bill pay Transfers
  22. 22. 24 Gardening microservices (and the before times)
  23. 23. 25
  24. 24. 26Source: @AreasAbandoned. 26
  25. 25. 27 Gardening platform & tools
  26. 26. Developers are the customers, the platform is the product 28@deniseyu21 Application Developers PIVOTAL CLOUD FOUNDRY DATABASE SERVICES SELF-SERVICE PORTAL 3RD PARTY INTEGRATIONS FEEDBACKLOOP FEEDBACK LOOP CI/CD MONITORING & LOGGING cf push cf push Platform Champion Product Manager Platform Engineers
  27. 27. 29 “The code to accomplish these tasks might be dozens of lines of JavaScript, which would be a trivial amount of development compared to what it takes to set up the servers with the proper environment to run the code.” Source: "Cloud Programming Simplified: A Berkeley View on Serverless Computing," a lot of people UC Berkeley.
  28. 28. Standardize & automate with a build pipeline 30 Sources: “Speed Thrills: How to Harness the Power of CI/CD for Your Development Team,” Ben Kamysz & Jared Ruckle, Pivotal, Aug 2017. CI/CD estimate based on the “The 12th Annual State of Agile Report” (2018) and “Survey Analysis: Agile Now at the Tipping Point - Here's How to Succeed,” Mike West, Gartner, June 2017, see also estimates from 2015. (<= 5 days)
  29. 29. Orchestration, Registry, Multi-cluster, Management, Conformance, Tenancy, API Based Encrypt, Isolation Segments, Orgs/Spaces, Audit, RBAC Loggregator, Metrics, Trace, Self Healing, Auto Scale Day2 Microservice (Blue/Green, Discover, Break, Config) APPLICATIONS API Buildpacks, Api Gateway, Routing/LB, Service Mesh, C2C CONTAINERS API >kubectl run {myimage} >cf push {mycode} >cf bind {myservice} Reactive Stream & Events, Less Code, Auto Run & Wire FUNCTIONS API >pfs create {myfunc:on} VMware AWS Google Azure Embedded OS (Windows & Linux) Network as API (Micro Segments) VMs & Storage as API (Cloud Provider Interface) Continuously Secured (Rotate, Repair, Repave) Platform-as-a- Product (Pipelines, Healthwatch) Service Broker, Marketplace Focus on developer productivity Source: Pivotal Platform overview.
  30. 30. 32
  31. 31. 33 The same as always
  32. 32. 34 The left overs: • Exploring and guiding org. wide technical decisions & services • Programming the organization • Talk with “The Business”
  33. 33. 35Source: “The New CIO: Leading IT the Mark Schwartz Way,” 2018 The CIO is the enterprise architect and arbitrates the quality of the IT systems in the sense that they promote agility in the future. The systems could be filled with technical debt but, at any given moment, the sum of all the IT systems is an asset and has value in what it enables the company to do in the future. The value is not just in the architecture but also in the people and the processes. It's an intangible asset that determines the company's future revenues and costs and the CIO is responsible for ensuring the performance of that asset in the future. “
  34. 34. More details 36 @cote | cote@pivotal.io • Book (free!): http://cote.io/books • Platform as a Product: • Recorded, more detailed presentation. • “Why You Should Treat Your Platform as a Product.” • Management: • Recorded enterprise architecture talk. • Recorded Creating a DevOps Culture talk. • Strategy, finance, & executives: • The Business Bottleneck work in progress.