Book has interesting parts, but seems to be trying to cover too broad a field, offering little of the tradeoffs promised in the title. Is is often very opinion

Book has interesting parts, but seems to be trying to cover too broad a field, offering little of the tradeoffs promised in the title. Is is often very opinionated about a highly technical area where the answer is always 'it depends', offering little balance of opinion before rapidly moving on to the next unrelated topic. e.g. Somewhere in a section on API versioning is the statement - "Modern services should generally be designed with no downtime required when updating the servers to a new version." As a grizzled developer in 2021 I would disagree with that, 24/7 365 up-time is hard and expensive, if the service doesn't require it then don't do it. There is a tradeoff between developer effort supporting multiple live versions and synchronization between teams to just stop the service and update everything. In the authors context it may be true, but the book is titled tradeoffs and all too often only offers the architecture astronauts uncosted ideal world opinion.