Neal Ford and Rebecca Parsons- Building Evolutionary Architectures (Evolution)
•Als PPTX, PDF herunterladen•
1 gefällt mir•1,045 views
An evolutionary architecture supports incremental, guided change across multiple dimensions. For many years, software architecture was described as the “parts that are hard to change later”. But then microservices showed that if architects build evolvability into the architecture, change becomes easier. This talk, based on our recent book, investigates the family of software architectures that support evolutionary change, along with how to build evolvable systems. Understanding how to evolve architecture requires understanding how architectural dimensions interact; we describe how to achieve appropriate coupling between components and services. Incremental change is critical for the mechanics of evolution; we cover how to build engineering and DevOps practices to support continuous change. Uncontrolled evolution leads to undesirable side effects; we cover how fitness functions build protective, testable scaffolding around critical parts to guide the architecture as it evolves. The software development ecosystem exists in a state of dynamic equilibrium, where any new tool, framework, or technique leads to disruption and the establishment of a new equilibrium. Predictability is impossible when the foundation architects plan against changes constantly in unexpected ways. Instead, prefer evolvability over predictability. This talk illustrates how to achieve evolutionary architectures and how to retrofit existing systems to support better evolution.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Neal Ford and Rebecca Parsons- Building Evolutionary Architectures (Evolution)
Ähnlich wie Neal Ford and Rebecca Parsons- Building Evolutionary Architectures (Evolution) (20)
Mehr von Thoughtworks
Mehr von Thoughtworks (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Neal Ford and Rebecca Parsons- Building Evolutionary Architectures (Evolution)
- 1. REBECCA PARSONS Chief Technology Officer @rebeccaparsons #EvolutionTW #ThoughtWorks NEAL FORD Director & Software Architect @neal4d
- 2. bUiLdiNG eVoLuTiONaRy ARcHitECtuREsSUPPORT CONSTANT CHANGE @neal4d nealford.com @patkua@rebeccaparsons
- 5. accessibility reliability repeatability accountability extensibility reproducibility accuracy failure transparency resilience adaptability fault-tolerance responsiveness administrability fidelity reusability affordability flexibility robustness agility inspectability safety auditability installability scalability autonomy integrity seamlessness availability interchangeability self-sustainability compatibility interoperability serviceability composability learnability supportability configurability maintainability securability correctness manageability simplicity credibility mobility stability customizability modifiability standards compliance debugability modularity survivability degradability operability sustainability determinability orthogonality tailorability demonstrability portability testability dependability precision timeliness deployability predictability traceability discoverability process capabilities transparency distributability producibility ubiquity durability provability understandability effectiveness recoverability upgradability efficiency relevance usability https://en.wikipedia.org/wiki/List_of_system_quality_attributes ility
- 6. evolvab ility accessibility reliability repeatability accountability extensibility reproducibility accuracy failure transparency resilience adaptability fault-tolerance responsiveness administrability fidelity reusability affordability flexibility robustness agility inspectability safety auditability installability scalability autonomy integrity seamlessness availability interchangeability self-sustainability compatibility interoperability serviceability composability learnability supportability configurability maintainability securability correctness manageability simplicity credibility mobility stability customizability modifiability standards compliance debugability modularity survivability degradability operability sustainability determinability orthogonality tailorability demonstrability portability testability dependability precision timeliness deployability predictability traceability discoverability process capabilities transparency distributability producibility ubiquity durability provability understandability effectiveness recoverability upgradability efficiency relevance usability evolvability
- 7. cHAnGe
- 14. everything changes all the time!
- 15. How is long term planning possible when things constantly change in unEXpECtEd ways?
- 17. EA Spreadsheet Penultima⬆︎e ✔️ definition ! verification
- 18. Once I’ve built an architecture, how can I prevent it from gradually degrading over time?
- 19. governance
- 20. Evolutionary Architecture An evolutionary architecture supports guided, incremental change across multiple dimensions.
- 21. Evolutionary Architecture An evolutionary architecture supports guided, incremental change across multiple dimensions. guided
- 22. guided evolutionary computing fitness function: a particular type of objective function that is used to summarize…how close a given design solution is to achieving the set aims.
- 23. guided
- 24. guided evolutionary computing fitness function: a particular type of objective function that is used to summarize…how close a given design solution is to achieving the set aims.
- 25. guided architectural fitness function: An architectural fitness function provides an objective integrity assessment of some architectural characteristic(s).
- 26. EA Spreadsheet Penultima⬆︎e ✔️ definition ! verification✔️ verification
- 27. Evolutionary Architecture An evolutionary architecture supports guided, incremental change across multiple dimensions. incremental guided
- 28. incremental
- 29. Penultima⬆︎e
- 30. Penultima⬆︎e
- 31. Penultima⬆︎e
- 32. Penultima⬆︎e
- 33. Penultima⬆︎e
- 34. Evolutionary Architecture An evolutionary architecture supports guided, incremental change across multiple dimensions. multiple dimensions incremental
- 36. Evolutionary Architecture An evolutionary architecture supports guided, incremental change across multiple dimensions. multiple dimensions
- 37. Agenda Definition Guided Change via Fitness Functions Incremental Change Governance
- 38. Evolutionary Architecture An evolutionary architecture supports guided, incremental change across multiple dimensions. guided
- 39. guided architectural fitness function: An architectural fitness function provides an objective integrity assessment of some architectural characteristic(s).
- 49. holistic triggered Holistic fitness functions must run in a specific (shared) context.
- 54. Synthetic Transactions Use synthetic transactions to test production systems.
- 55. Correlation IDs ID: 123 ID: 123 ID: 123 Use correlation IDs to track down nasty bugs
- 64. Agenda Definition Guided Change via Fitness Functions Incremental Change Governance
- 65. incremental
- 68. Deployment Pipeline + Fitness Functions
- 69. Agenda Definition Guided Change via Fitness Functions Incremental Change Governance
- 70. Implementing Fitness Functions Protecting architectural characteristics Automating governance
- 71. maintainable?
- 72. Testable tecture characteristics are evaluable
- 85. Putting evolutionary architecture into Practice
- 86. Mechanics 1. Identify dimensions affect by evolution
- 87. 1. Identify dimensions affect by evolution
- 88. Mechanics 1. Identify dimensions affect by evolution 2. Define Fitness Function(s) for Each Dimension
- 89. 2. Define Fitness Function(s) for Each Dimension
- 90. Mechanics 1. Identify dimensions affect by evolution 2. Define Fitness Function(s) for Each Dimension 3. Use Deployment Pipelines to Automate Fitness Functions
- 91. 3. Use Deployment Pipelines to Automate Fitness Functio
- 92. Mechanics 1. Identify dimensions affect by evolution 2. Define Fitness Function(s) for Each Dimension 3. Use Deployment Pipelines to Automate Fitness Functions
- 93. Mechanics 1. Identify dimensions affect by evolution 2. Define Fitness Function(s) for Each Dimension 3. Use Deployment Pipelines to Automate Fitness Functions
- 94. Agenda Definition Guided Change via Fitness Functions Incremental Change Governance
- 97. ▫ It decides whether or not to run the try block, ▫ Randomizes the order in which use and try blocks are run, ▫ Measures the durations of all behaviors, ▫ Compares the result of try to the result of use, ▫ Swallows (but records) any exceptions raised in the try block ▫ Publishes all this information.
- 101. 4 days 24 hours/ no mismatches or slow cases > 10,000,000 comparisons > 10,000,000 comparisons
- 102. Evolutionary Architecture An evolutionary architecture supports guided, incremental change across multiple dimensions.
- 103. Building Evolutionary Architectures For more information: http://evolutionaryarchitecture.com
Hinweis der Redaktion
- Rebecca
- Pat
- Pat
- For example, a company that handles international fund transfers might design a specific, continuous, holistic fitness function that stress tests security, modeled after the way that the Simian Army (covered in Chapter 3) stresses infrastructure.
- Unit test to verify architectural integrity Examples
- Integration tests to ensure proper co-evolution
- Security and scaling interaction
- endpoint testing
- Balancing and tradeoffs
- Accordion: Radiolab & foxes
- Neal
- Rebecca
- PAT
- A lot of teams don’t identify what they are building the architecture for. It doesn’t take long to identify which ones are relevant. Domain = finance, banking, retail, entertainment
- Define how you know you are done. DoD for each dimension (fuzzier, not so clear)
- Examples: Add in performance testing pipelines (memory leak) - even a simple smaller constrained Security, modularity checks Chaos engineering - testing the holistic fitness functions
- Shortly after the deploy, the accuracy graph shows that experiments are being run at the right frequency and that mismatches are very few.
- Graphing the errors/mismatches on their own shows their frequency in more detail. Our tooling captures metadata all these mismatches so they can be analyzed later.
- Although it's too early to tell, shortly after the initial deploy the performance characteristics look extremely promising. The vertical axis is time, in milliseonds. Percentiles for the old and new code are shown in blue and green, respectively.
- Rebecca