Software Architecture

I like the books from the SEI (Software Engineering Institute), although its been a few years that I bought new ones (or lend a few to read through). The "Software Architecture in Practice" by Len Bass, Paul Clements and Rick Kazman is one that I do still consult. Another one is "Documenting Software Architecture" by Paul Clements, Felix Bachmann, Len Bass and a few others.

While I also have "Evaluating Software Architectures" I was a bit more disappointed there, although that might be because I was expecting more content steering whereas the book is more about the process of evaluation (using methodologies like ATAM). My current job is strongly within the non-functional area, so I might be more biased there.

These books are however quite heavy. It might be better to first focus on lightweight architecture practices and pattern books/resources, as well as see how rigid software architecture is handled within your company. There is little value in massively focusing on architectural governance, frameworks, methodologies, processes and the like if the organization isn't tuned to this.

The Practical Architecture Process is probably the best distillation I've read.

Alongside that there's the classics, Enterprise Integration Patterns, a DDD book of your choosing, Newman's Microservices.

I'm a big fan of ReST In Practice, though nobody cares about ReST any more, and Simon Brownwork is great, particularly the C4 model.

Mostly, unfortunately, you have to learn by doing. Design a thing, document your assumptions and constraints, and see if the design still makes sense 5 years later.