Software Architecture in Practice (SEI Series in Software Engineering)

I was very impressed with this book. It's underrated. I've read many software architecture books before that weren't practical. This one definitely is. He makes it easy to apply any parts of this you want to your projects. There's a lot here, so don't worry if you can't use all of it. Just pick the parts that make sense for your team.

As I finally have more time to read during this holiday season, a book on the top of my list is the 4th edition of Software Architecture in Practice.Yes, I am biased because I research software architectures, and I used the first edition of the book when I was a graduate student more than 20 years ago.When I started reading the latest edition, I was pleasantly surprised to spot my name in the book's acknowledgement section together with Phillip Laplante, CSDP, PE, MBA, PhD. I thank Rick Kazman for the credit!The 4th edition of Software Architecture in Practice is more relevant than ever due to the increasing need for a holistic view of our systems constantly evolving.I strongly recommend this book for all the software engineers out there, both seasoned and just beginning. I will undoubtedly read this book cover to cover fourth time again, and I am looking forward to reading the new sections added on virtualization, interfaces, mobility, and the cloud.

Len Bass Paul Clements and Rick Kazman have packed this 4th edition of Software Architecture in Practice with a lot of new and very relevant material-- new quality attributes like Deployability and Energy Efficiency- tactics analysis questionnaires for each quality attribute- chapters on architecture considerations for virtualization, cloud computing, and mobile computing- managing architecture debtDefinitely worth the investment to get a copy. I've already been consulting my new copy for a project I'm starting - the Deployability tactics and patterns and the chapter on the Role of the Architect are giving me material that I am using to talk effectively with stakeholders.

It is useful. Beware, however, that instead of software architecture (high-level design) it describes all of software design (largely detailed design), so that approx. 80% of this book is not about big decisions, but about tiny little microdecisions with a huge amount of information required for you to have to decide.I do not find the book practical at all. It is useful to remind you of non-functional requirements and how they can be satisfied, but does not cover Azure, AWS, or Google Cloud and I do not see MS Visio or SparxSystems Enterprise Architect covered either, and I do not even see any online content that would provide practical templates, and I do not think it covers Agile architecting (so it is waterfall), and it does not seem to be put in the context of SDLC, so it does not cover requirements very well, and it does not provide scientific theories, such as design theory that would explain software architecture.In many ways it is useful, but architecture does not exist in a vacuum and the book fails to teach. It is only useful when you already know everything and you want to be extra thorough, so instead of carrying all in your head, you use extra thorough lists of bullet points and models from the book. They can inform you while doing something, but in practice it is inefficient and when you instead read the design theory you might as well skip this book and go elsewhere, such as the SWEBOK to get a summary.This book kind of feels as if somebody needed to produce new knowledge at any cost. Probably, that's what the software engineering institute does. I cannot imagine any practitioner following this book and I have never seen an of my colleagues at work in my entire career to put this book on their desk and refer to it at work. So, while it is useful for self-englightenment and similar purposes, IT architects are using real tools and solving problems by composing systems that they know to give them the solution. In this aspect, the book is not required. Show me who from the real world needs this book and why, which real-world project has a team of IT architects all of whom follow this book.

I was surprised that I didn't like this book more than I did. A lot of people refer to it as the most influential book out there. I found it a bit dry. One of the more annoying things is that they force all of the quality attributes through a format that is pretty mechanical and abstract. I kept skipping that part as it was a distraction. The most useful part in my opinion was the "additional reading" sections.There were some errata but nowhere to report them. One was absolutely horrifying. At some point it incorrectly explains how load balancers work but with such a fundamental mistake that it gives me pause about the validity of the whole book. (It doesn't seem to understand that a load balancer returns the HTTP response to the caller in a synchronous manner.)Writing about software architecture seems to be slippery. In the abstract it's hard to get right. Best book I've seen overall by far is "Designing Data-Intensive Systems" though it focuses specifically on Distributed Systems. Fairbanks is abstract but ok. Neal Ford's "Fundamentals of Software Architecture" is somewhat practical but a little more fundamental as its name suggests.

Llegó en mal estado y ni siquiera iba empacado en plástico. Llegó como si fuera usado y con humedad

Haven't read even the third part and have it fully torn apart.

Todo lo que debe tener en cuenta un arquitecto para no entrar demasiado en el producto ni salirse del todo, muy buenos tips para saber manejar las qualities y attributos de un sistema de cara a un negocio.