Prerequisites for evolutionary architecture
•
0 likes•27 views
This document discusses prerequisites for evolutionary architecture. It advocates separating release from deployment to allow for fast feedback loops. Key techniques include domain-driven design, event storming, feature toggling, continuous integration and delivery, and database schema flexibility. Automated testing, monitoring, and metrics collection are also recommended to facilitate feedback. An adaptive culture that embraces change, defers decisions, and recognizes software's importance is seen as critical for evolutionary architecture.
![WHO AM I?
WHO AM I?
Name: Chris Howe-Jones [Technical Navigator]
Twitter: @agile_geek
Github: https://github.com/chrishowejones
Website: https://www.devcycle.co.uk](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (17)
Similar to Prerequisites for evolutionary architecture
Similar to Prerequisites for evolutionary architecture (20)
Recently uploaded
Recently uploaded (20)
Prerequisites for evolutionary architecture
- 1. PREREQUISITES FOR PREREQUISITES FOR EVOLUTIONARY EVOLUTIONARY ARCHITECTURE ARCHITECTURE CHRIS HOWE-JONES CHRIS HOWE-JONES 12TH NOVEMBER 2020 12TH NOVEMBER 2020
- 2. WHO AM I? WHO AM I? Name: Chris Howe-Jones [Technical Navigator] Twitter: @agile_geek Github: https://github.com/chrishowejones Website: https://www.devcycle.co.uk
- 3. WHY EVOLUTIONARY ARCHITECTURE? WHY EVOLUTIONARY ARCHITECTURE? The only constant is change!
- 4. WHY EVOLUTIONARY ARCHITECTURE? WHY EVOLUTIONARY ARCHITECTURE? The only constant is change! What is change?
- 5. WHY EVOLUTIONARY ARCHITECTURE? WHY EVOLUTIONARY ARCHITECTURE? The only constant is change! What is change? "the process of replacing something with something new or different; a thing that is used to replace something"
- 6. WHY EVOLUTIONARY ARCHITECTURE? WHY EVOLUTIONARY ARCHITECTURE? The only constant is change! What is change? What is evolution? "the process of replacing something with something new or different; a thing that is used to replace something"
- 7. WHY EVOLUTIONARY ARCHITECTURE? WHY EVOLUTIONARY ARCHITECTURE? The only constant is change! What is change? What is evolution? "the process of replacing something with something new or different; a thing that is used to replace something" "the gradual development of something."
- 9. KEY CHARACTERISTICS OF EVOLUTION KEY CHARACTERISTICS OF EVOLUTION Adaptation
- 10. MECHANISMS OF ADAPTATION MECHANISMS OF ADAPTATION
- 11. MECHANISMS OF ADAPTATION MECHANISMS OF ADAPTATION New generations.
- 12. MECHANISMS OF ADAPTATION MECHANISMS OF ADAPTATION New generations. Feedback.
- 13. MECHANISMS OF ADAPTATION MECHANISMS OF ADAPTATION New generations. Feedback. Room to fail (adaptations that do not survive).
- 14. MECHANISMS OF ADAPTATION MECHANISMS OF ADAPTATION
- 15. MECHANISMS OF ADAPTATION MECHANISMS OF ADAPTATION Short cycles between generations.
- 16. MECHANISMS OF ADAPTATION MECHANISMS OF ADAPTATION Short cycles between generations. Ability to fallback to earlier successful generations.
- 17. MECHANISMS OF ADAPTATION MECHANISMS OF ADAPTATION Short cycles between generations. Ability to fallback to earlier successful generations. Reactive to ecosystem
- 18. MECHANISMS OF ADAPTATION MECHANISMS OF ADAPTATION Short cycles between generations. Ability to fallback to earlier successful generations. Reactive to ecosystem Impact on ecosystem
- 19. TRANSLATED TO SOFTWARE TRANSLATED TO SOFTWARE
- 20. TRANSLATED TO SOFTWARE TRANSLATED TO SOFTWARE Separate deployment from release.
- 21. TRANSLATED TO SOFTWARE TRANSLATED TO SOFTWARE Separate deployment from release. Fast feedback In development In production
- 22. TRANSLATED TO SOFTWARE TRANSLATED TO SOFTWARE Separate deployment from release. Fast feedback In development In production Appropriate feedback Metrics for architecturally important aspects
- 23. TRANSLATED TO SOFTWARE TRANSLATED TO SOFTWARE Separate deployment from release. Fast feedback In development In production Appropriate feedback Metrics for architecturally important aspects Responsive culture
- 24. PICK YOUR CONSTRAINTS PICK YOUR CONSTRAINTS
- 30. MATERIALS MATTER MATERIALS MATTER Because the constraints they introduce direct behaviour
- 31. SEPARATE RELEASE FROM DEPLOYMENT SEPARATE RELEASE FROM DEPLOYMENT
- 32. FEEDBACK FEEDBACK Data (Hypothesis) Driven Development
- 33. FEEDBACK BETWEEN ECOSYSTEMS FEEDBACK BETWEEN ECOSYSTEMS
- 34. FEEDBACK IN MICRO-ECOSYSTEM FEEDBACK IN MICRO-ECOSYSTEM
- 35. FEEDBACK IN BIOTOPE FEEDBACK IN BIOTOPE
- 36. FEEDBACK IN BIOME FEEDBACK IN BIOME
- 37. FEEDBACK IN BIOSPHERE FEEDBACK IN BIOSPHERE
- 38. TL;DR TL;DR Separate Release from Deployment
- 39. TL;DR TL;DR Separate Release from Deployment DDD - contexts, aggregates [Discovery]
- 40. TL;DR TL;DR Separate Release from Deployment DDD - contexts, aggregates [Discovery] Event storming [Discovery]
- 41. TL;DR TL;DR Separate Release from Deployment DDD - contexts, aggregates [Discovery] Event storming [Discovery] Feature toggling [Implementation]
- 42. TL;DR TL;DR Separate Release from Deployment DDD - contexts, aggregates [Discovery] Event storming [Discovery] Feature toggling [Implementation] Branch by abstraction [Implementation]
- 43. TL;DR TL;DR Separate Release from Deployment DDD - contexts, aggregates [Discovery] Event storming [Discovery] Feature toggling [Implementation] Branch by abstraction [Implementation] CI [Implementation]
- 44. TL;DR TL;DR Separate Release from Deployment DDD - contexts, aggregates [Discovery] Event storming [Discovery] Feature toggling [Implementation] Branch by abstraction [Implementation] CI [Implementation] CD [Implementation]
- 45. TL;DR TL;DR Separate Release from Deployment DDD - contexts, aggregates [Discovery] Event storming [Discovery] Feature toggling [Implementation] Branch by abstraction [Implementation] CI [Implementation] CD [Implementation] Immutable servers [Implementation]
- 46. TL;DR TL;DR Separate Release from Deployment DDD - contexts, aggregates [Discovery] Event storming [Discovery] Feature toggling [Implementation] Branch by abstraction [Implementation] CI [Implementation] CD [Implementation] Immutable servers [Implementation] Dark/Canary/Blue-Green deployments [Implementation]
- 47. TL;DR TL;DR Separate Release from Deployment DDD - contexts, aggregates [Discovery] Event storming [Discovery] Feature toggling [Implementation] Branch by abstraction [Implementation] CI [Implementation] CD [Implementation] Immutable servers [Implementation] Dark/Canary/Blue-Green deployments [Implementation] Schema on Read DBs [Implementation]
- 52. TL;DR TL;DR Feedback Automated testing CI CD Automated Observability (alerting, logging, monitoring, etc)
- 53. TL;DR TL;DR Feedback Automated testing CI CD Automated Observability (alerting, logging, monitoring, etc) Metrics at all levels
- 54. TL;DR TL;DR Feedback Automated testing CI CD Automated Observability (alerting, logging, monitoring, etc) Metrics at all levels Visualisation of work ows
- 55. TL;DR TL;DR Feedback Automated testing CI CD Automated Observability (alerting, logging, monitoring, etc) Metrics at all levels Visualisation of work ows Retrospectives
- 57. TL;DR TL;DR Culture Pick your constraints (Materials matter)
- 58. TL;DR TL;DR Culture Pick your constraints (Materials matter) Stay small for as long as possible
- 59. TL;DR TL;DR Culture Pick your constraints (Materials matter) Stay small for as long as possible Recognise that software is core to most orgs
- 60. TL;DR TL;DR Culture Pick your constraints (Materials matter) Stay small for as long as possible Recognise that software is core to most orgs Defer design decisions
- 61. TL;DR TL;DR Culture Pick your constraints (Materials matter) Stay small for as long as possible Recognise that software is core to most orgs Defer design decisions Simplify (not same as easy!)
- 62. TL;DR TL;DR Culture Pick your constraints (Materials matter) Stay small for as long as possible Recognise that software is core to most orgs Defer design decisions Simplify (not same as easy!) Architecture is a social & group process