This book demonstrates how decisions in architecture should be made - if at all. Chapters usually start with some kind of scenario and a given problem. Then different solutions to the problem are presented, followed by details about the trade-offs. And when the decision has been made it is documented in an ADR. Besides that, it contains the usual things you can find in a book about architecture like microservices yes/no, big ball of mud yes/no and so on.
Software Architecture: The Hard Parts: Modern Trade-Off Analyses for Distributed Architecturesvon Neal FordO'Reilly