Fundamentals of Software Architecture

The book manages well to equally give generic advice on how to approach the role of a software architect on the one hand and provides lots of practical tips regarding actual architecture concepts on the other hand. It also emphases the social components such as having a lot of meetings and selling and defending your decisions to management ,developers and other stakeholders.

I recommend the book especially to people transitioning to an architect role.

An aspect I missed a little bit is explicit advice on how to deal with legacy and external systems since those usually have to be considered when doing architecture and are virtually present everywhere, at least in non-trivial applications. This might not be strictly necessary in an introduction book but could have been emphasised since the book gives a rather pragmatic overview to the role.

A very basic book on the topic. It has good parts, but a reader must be very careful because it's full of bullshit advice.

The writing is boring and overly long. I have no idea why could anybody call this a good book.

Introduces a lot of concepts and techniques you can use, but also looks at the broader picture such as communications.

A lot more applicable (and practical) advice compared to e.g. the books by Len Bass.

This is a great book about architecture and actually one of my few, that is actually up-to-date and covers topics of my current project like Architecture Decisions Records (ADR). I also likes the comparison with the ratings for different architectures, haven't seen something like this so far, although I know the are different trade-offs for each of them.



I always like books, when they also go into detail about the social and leadings aspects of the architect role, because this is usually something we technical folks have problems with.