Essential Software Architecture Paperback – 8 Oct. 2014

This book begins by defining what software architecture is - a term that can be mean different things to different people and different organisations. It then defines and explains all key non-functional requirements (performance, scalability, security etc) things that I think everyone would agree are very important in software architecture. It then explains various architectural approaches used in enterprise systems. This includes web services, message orientated systems, model driven architecture, aspect orientated architectures. There is also a case study which shows how some of concepts described can be applied.My favourie part was on message orientated architectures. All the fundamental and sophisticated aspects are very explained. These include: the asychronous nature of it, the way you can cluster message ques and brokers, the hierachial naming formats in publish subscribe message topics and the different approaches to reliability (best effort, persistent and transactional). There was also some really good discussion regarding the background and importance of message brokers.As well as technical concepts there are also some interesting sections on architectural processes, documentation and even my old favourite UML.This book serves as a very good reminder to the importance of software architecture - especially in enterprise systems. Architectural approaches don't just need to be properly understood, they need to be compared with other approaches especially with respect to the non-functional requirements that are important to your system.

The book constantly name drops Java technologies and concerns itself with server architectures. As I write stand-alone C++ applications and know neither Java nor server stuff this is next to useless to me. The chapter on quality attributes was good though probably not general enough.In this context I don't understand either the description or the three previous reviews. Am returning this, luckily I also bought Just Enough Software Architecture: A Risk-Driven Approach at the same time so I do have some idea of modern formal software architecture when it comes to report writing in the new job.

un po datato forse ma una buona lettura

In general, the book is very nice if you're a bit lost about what a SW architect should be. In my case, I was really curious about the job of SW architect, and this book answered many of my questions during the first chapters and specially thanks to the case study presented in the book.There are other aspects that could be improved or more deeply explained, such as Aspect-Oriented Programming or Model-Driven Development. I guess that they're not so practically covered because they're emerging approaches more used in academia than in industry. However, the part of middleware, one of the most complex pieces of SW (and widely used in almost any application nowadays), is fully explained with lots of examples.I really enjoyed reading the book and I think I learned lots of stuff. Maybe it's not the book for a SW architect with years of experience, but yes for those who expect to become one, or who want to know more about the tasks to be done by this role.

It provides general information about software architecture but not details. It covers many topics in this domain but in some domains like web services it doesn't give enough architectural view to readers.