Software Architecture Metrics: Case Studies to Improve the Quality of Your Architecture

We have a club tonight.Code of Architecturelast stream I wrote a book called Building Evolutionary Architecture, and I decided to read a book about metrics in software architecture. And so fortunately, I was able to read most of this book on the road between Moscow and Sochi. And I flew to Sochi yesterday to the SouthHub Camp for CTO, where I also have a short performance today.

But if you go back to the subject of the book,

• modest volume - of the order of magnitude 200 page
• in her 10 The authors, that's a big deal:) Each author gives his or her perspective on metrics and how to evaluate them. And since everyone has their own books, it is easy to guess their view. David Farley talks about CI/CD metrics (co-authorContinuous Delivery") Eóin Woods talks about metrics as part of a continuous architecture approach (co-authorContinuous Architecture in Practice") In addition, the author of each chapter recalls evolutionary architecture and fitness functions, even if it does not fit well into his story - apparently, one of the goals of this book was to popularize the approach of the author. I like the case studies set – there is a lot to think about and make architectural changes more focused and measurable.

By the way, the authors of this collection say that those who read the book will learn: *- Measure how well your software architecture is meeting your goals

• Choose the right metrics to track (and skip the ones you don't need)
• Improve observability, testability, and deployability
• Prioritize software architecture projects
• Build insightful and relevant dashboards* And this book really deals with all these topics... At the helicopter view level:)

#SoftwareArchitecture #SoftwareDevelopment #Architecture #SystemDesign #Metrics #Management #Processes #ContinuousDelivery