I'd like to thank you for such a great book and the opportunity to ask questions, this go to everyone who is coordinating this the forums.
after going through the table of contents, I got the impression that the book is about mastering and enhancing the qualities of a system, that is a single self contained system if I may say, however in today's landscape we barely see systems "or code" running in isolation from other systems, usually in the enterprise, services are composed of several systems that interact to serve the business. do you cover such set up or scale in the book?
another question I have is about architecture such as microservices, where the system itself is distributed as a set of collaborating services. how do you scale the quality attributes from one system to cover all of these as a whole.
thanks for your interest in the book and your kind words.
Indeed, the focus of the book is on a small software unit, because I think that's the ideal size to showcase and compare many different software qualities.
As you say, a real system is composed of many parts, interacting locally or over a network, perhaps as microservices.
Even though I don't address distributed systems per se, the principles of my book apply equally well to each part of the system.
Namely, each part is subject to the careful balance of software qualities that I try to illuminate in the book.
Now, I don't mean to imply that separately optimising each part will lead to a globally optimised distributed system, but it's a step in the right direction.
Any large system will need architecture-level analyses and decisions that I don't cover in the book.
In fact, I'd expect those high-level decisions to guide the unit-level design toward a balance of qualities that is appropriate to the context.