TLDR : Evolvability as a non functional requirement motivated, defined and operationalized. 5/5
Review
I was engrossed in this book for 3 days and did nothing much except basic life rituals which goes to show the power of the book. First of all this book is very well written for a software architecture book and packed with so many nuggets of knowledge that I ended up highlighting 1/3rd of the book.
We all know that those PPT diagrams of Architecture are so irrelevant when it comes to evolution of software over time and the rapid changes in technology which is explained by the book. Hence this book counsels to build changeability into the architecture which it terms evolvability. Although the word evolution is from biology , this book envisions guidance rather than a more resource intensive natural selection.
When I was doing my Subscription Engine product a decade ago, I went around looking for software that could encode Architectural Validation when developers checkin code. I landed up with using Crap4J (still available) and Lattix. This book aims to create a "fitness function" (atomic/holistic, triggered/continual, static/dynamic, automated/manual, temporal, intentional/emergent, domain/non domain) for key architectural characteristics which are measurable and that protect the key characteristics of architecture. It gives some examples using Jdepends. It then talks about structuring teams as per your Architecture (Inverse Conway). It then talks about how CI/CD can be used for fitness functions.
The book further discusses the context of fitness functions, incremental change, coupling for a vast variety of architecture including big ball of mud, microservices, microkernel, broker, mediator, SOA and Serverless . This is the most invaluable part of the book as a quick reference.
An important chapter talks about evolutionary data and various methods to make schemas evolutionary given the transactionality of system using patterns like routing, feature toggles and an innovative expand/contract mechanism. Data geeks will love this.
The next chapter goes about the howto aspects of identifying dimensions, fitness functions of each dimension and automating the process. It has important insights on migration of architectures and dealing with COTS software and some caveats.The guidelines for evolutionary architecture like removing variability, reversible decision, anti corruption, sacrificial architectures, service templates, external change mitigation, libraries vs frameworks, service versioning, evolve over predict are very useful.
The next chapter talks about anti patterns and pitfalls (I have read the book on same) like Vendor King, Leaky Abstractions, Last 10% trap (nice one), Resume driven development, Inappropriate Governance, Reuse Abuse, Slow releases, Over Customization, Reporting (good points) and Planning Horizons which were very insightful.
The last chapter is more of the practice aspect of evolutionary architectures which include cross functional teams, organization around business capabilities, product over project, culture and budgeting. It further talks about heuristics like highest value, low hanging fruit, infrastructure and testing to select things to write fitness functions first. The remarks on AI and Generative Testing for fitness functions was very interesting. The importance of low cycle time which is a sine qua non to fitness functions was something repeated in multiple places.
Overall, this is one book I plan to come back to as I work with 3 products in my product suite at work and will influence most of my future work too.
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet or computer – no Kindle device required. Learn more
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera, scan the code below and download the Kindle app.
Flip to back Flip to front
Free Delivery
The product is eligible for Free delivery. Learn more
There is a newer edition of this item:
Building Evolutionary Architectures: Automated Software Governance
₹4,528.00
(4)
Usually dispatched in 10 to 11 days.
₹4,528.00
(4)
Usually dispatched in 10 to 11 days.
Frequently bought together
- +
- +
Total price:
To see our price, add these items to your cart.
Choose items to buy together.
Customers who viewed this item also viewed
Page 1 of 1 Start overPage 1 of 1
Evolvability as a non functional requirement motivated, defined and operationalized. 5/5
Reviewed in India on 24 January 2018
TLDR : Evolvability as a non functional requirement motivated, defined and operationalized. 5/5ReviewI was engrossed in this book for 3 days and did nothing much except basic life rituals which goes to show the power of the book. First of all this book is very well written for a software architecture book and packed with so many nuggets of knowledge that I ended up highlighting 1/3rd of the book.We all know that those PPT diagrams of Architecture are so irrelevant when it comes to evolution of software over time and the rapid changes in technology which is explained by the book. Hence this book counsels to build changeability into the architecture which it terms evolvability. Although the word evolution is from biology , this book envisions guidance rather than a more resource intensive natural selection.When I was doing my Subscription Engine product a decade ago, I went around looking for software that could encode Architectural Validation when developers checkin code. I landed up with using Crap4J (still available) and Lattix. This book aims to create a "fitness function" (atomic/holistic, triggered/continual, static/dynamic, automated/manual, temporal, intentional/emergent, domain/non domain) for key architectural characteristics which are measurable and that protect the key characteristics of architecture. It gives some examples using Jdepends. It then talks about structuring teams as per your Architecture (Inverse Conway). It then talks about how CI/CD can be used for fitness functions.The book further discusses the context of fitness functions, incremental change, coupling for a vast variety of architecture including big ball of mud, microservices, microkernel, broker, mediator, SOA and Serverless . This is the most invaluable part of the book as a quick reference.An important chapter talks about evolutionary data and various methods to make schemas evolutionary given the transactionality of system using patterns like routing, feature toggles and an innovative expand/contract mechanism. Data geeks will love this.The next chapter goes about the howto aspects of identifying dimensions, fitness functions of each dimension and automating the process. It has important insights on migration of architectures and dealing with COTS software and some caveats.The guidelines for evolutionary architecture like removing variability, reversible decision, anti corruption, sacrificial architectures, service templates, external change mitigation, libraries vs frameworks, service versioning, evolve over predict are very useful.The next chapter talks about anti patterns and pitfalls (I have read the book on same) like Vendor King, Leaky Abstractions, Last 10% trap (nice one), Resume driven development, Inappropriate Governance, Reuse Abuse, Slow releases, Over Customization, Reporting (good points) and Planning Horizons which were very insightful.The last chapter is more of the practice aspect of evolutionary architectures which include cross functional teams, organization around business capabilities, product over project, culture and budgeting. It further talks about heuristics like highest value, low hanging fruit, infrastructure and testing to select things to write fitness functions first. The remarks on AI and Generative Testing for fitness functions was very interesting. The importance of low cycle time which is a sine qua non to fitness functions was something repeated in multiple places.Overall, this is one book I plan to come back to as I work with 3 products in my product suite at work and will influence most of my future work too.
Reviewed in India on 24 January 2018
Images in this review
Top review from India
There was a problem filtering reviews right now. Please try again later.
Reviewed in India 🇮🇳 on 24 January 2018
Review
I was engrossed in this book for 3 days and did nothing much except basic life rituals which goes to show the power of the book. First of all this book is very well written for a software architecture book and packed with so many nuggets of knowledge that I ended up highlighting 1/3rd of the book.
We all know that those PPT diagrams of Architecture are so irrelevant when it comes to evolution of software over time and the rapid changes in technology which is explained by the book. Hence this book counsels to build changeability into the architecture which it terms evolvability. Although the word evolution is from biology , this book envisions guidance rather than a more resource intensive natural selection.
When I was doing my Subscription Engine product a decade ago, I went around looking for software that could encode Architectural Validation when developers checkin code. I landed up with using Crap4J (still available) and Lattix. This book aims to create a "fitness function" (atomic/holistic, triggered/continual, static/dynamic, automated/manual, temporal, intentional/emergent, domain/non domain) for key architectural characteristics which are measurable and that protect the key characteristics of architecture. It gives some examples using Jdepends. It then talks about structuring teams as per your Architecture (Inverse Conway). It then talks about how CI/CD can be used for fitness functions.
The book further discusses the context of fitness functions, incremental change, coupling for a vast variety of architecture including big ball of mud, microservices, microkernel, broker, mediator, SOA and Serverless . This is the most invaluable part of the book as a quick reference.
An important chapter talks about evolutionary data and various methods to make schemas evolutionary given the transactionality of system using patterns like routing, feature toggles and an innovative expand/contract mechanism. Data geeks will love this.
The next chapter goes about the howto aspects of identifying dimensions, fitness functions of each dimension and automating the process. It has important insights on migration of architectures and dealing with COTS software and some caveats.The guidelines for evolutionary architecture like removing variability, reversible decision, anti corruption, sacrificial architectures, service templates, external change mitigation, libraries vs frameworks, service versioning, evolve over predict are very useful.
The next chapter talks about anti patterns and pitfalls (I have read the book on same) like Vendor King, Leaky Abstractions, Last 10% trap (nice one), Resume driven development, Inappropriate Governance, Reuse Abuse, Slow releases, Over Customization, Reporting (good points) and Planning Horizons which were very insightful.
The last chapter is more of the practice aspect of evolutionary architectures which include cross functional teams, organization around business capabilities, product over project, culture and budgeting. It further talks about heuristics like highest value, low hanging fruit, infrastructure and testing to select things to write fitness functions first. The remarks on AI and Generative Testing for fitness functions was very interesting. The importance of low cycle time which is a sine qua non to fitness functions was something repeated in multiple places.
Overall, this is one book I plan to come back to as I work with 3 products in my product suite at work and will influence most of my future work too.
Verified Purchase
Evolvability as a non functional requirement motivated, defined and operationalized. 5/5
Reviewed in India 🇮🇳 on 24 January 2018
TLDR : Evolvability as a non functional requirement motivated, defined and operationalized. 5/5Reviewed in India 🇮🇳 on 24 January 2018
Review
I was engrossed in this book for 3 days and did nothing much except basic life rituals which goes to show the power of the book. First of all this book is very well written for a software architecture book and packed with so many nuggets of knowledge that I ended up highlighting 1/3rd of the book.
We all know that those PPT diagrams of Architecture are so irrelevant when it comes to evolution of software over time and the rapid changes in technology which is explained by the book. Hence this book counsels to build changeability into the architecture which it terms evolvability. Although the word evolution is from biology , this book envisions guidance rather than a more resource intensive natural selection.
When I was doing my Subscription Engine product a decade ago, I went around looking for software that could encode Architectural Validation when developers checkin code. I landed up with using Crap4J (still available) and Lattix. This book aims to create a "fitness function" (atomic/holistic, triggered/continual, static/dynamic, automated/manual, temporal, intentional/emergent, domain/non domain) for key architectural characteristics which are measurable and that protect the key characteristics of architecture. It gives some examples using Jdepends. It then talks about structuring teams as per your Architecture (Inverse Conway). It then talks about how CI/CD can be used for fitness functions.
The book further discusses the context of fitness functions, incremental change, coupling for a vast variety of architecture including big ball of mud, microservices, microkernel, broker, mediator, SOA and Serverless . This is the most invaluable part of the book as a quick reference.
An important chapter talks about evolutionary data and various methods to make schemas evolutionary given the transactionality of system using patterns like routing, feature toggles and an innovative expand/contract mechanism. Data geeks will love this.
The next chapter goes about the howto aspects of identifying dimensions, fitness functions of each dimension and automating the process. It has important insights on migration of architectures and dealing with COTS software and some caveats.The guidelines for evolutionary architecture like removing variability, reversible decision, anti corruption, sacrificial architectures, service templates, external change mitigation, libraries vs frameworks, service versioning, evolve over predict are very useful.
The next chapter talks about anti patterns and pitfalls (I have read the book on same) like Vendor King, Leaky Abstractions, Last 10% trap (nice one), Resume driven development, Inappropriate Governance, Reuse Abuse, Slow releases, Over Customization, Reporting (good points) and Planning Horizons which were very insightful.
The last chapter is more of the practice aspect of evolutionary architectures which include cross functional teams, organization around business capabilities, product over project, culture and budgeting. It further talks about heuristics like highest value, low hanging fruit, infrastructure and testing to select things to write fitness functions first. The remarks on AI and Generative Testing for fitness functions was very interesting. The importance of low cycle time which is a sine qua non to fitness functions was something repeated in multiple places.
Overall, this is one book I plan to come back to as I work with 3 products in my product suite at work and will influence most of my future work too.
Images in this review
Top reviews from other countries
Amazon Customer
Some good advice but sparse
Reviewed in the United Kingdom 🇬🇧 on 8 October 2019Verified Purchase
Remo Biagioni
A hugely disappointing book
Reviewed in the United Kingdom 🇬🇧 on 26 April 2020Verified Purchase
PerivaleElvis
Brilliant book
Reviewed in the United Kingdom 🇬🇧 on 20 February 2019Verified Purchase
jameshd
Good, but...
Reviewed in the United Kingdom 🇬🇧 on 6 April 2018Verified Purchase
MS
Good and easy to read book
Reviewed in the United Kingdom 🇬🇧 on 18 July 2020Verified Purchase
