Essential Software Architecture and over 2 million other books are available for Amazon Kindle . Learn more
FREE Delivery in the UK.
Only 1 left in stock (more on the way).
Dispatched from and sold by Amazon.
Gift-wrap available.
Essential Software Archit... has been added to your Basket
Used: Like New | Details
Sold by a_bargain_book
Condition: Used: Like New
Trade in your item
Get a £15.21
Gift Card.
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See all 2 images

Essential Software Architecture Hardcover – 6 May 2011

See all 2 formats and editions Hide other formats and editions
Amazon Price New from Used from
Kindle Edition
"Please retry"
"Please retry"
£26.14 £29.99
£53.99 FREE Delivery in the UK. Only 1 left in stock (more on the way). Dispatched from and sold by Amazon. Gift-wrap available.

Frequently Bought Together

Essential Software Architecture + Enterprise Architecture Patterns: Practical Solutions for Recurring IT-Architecture Problems
Price For Both: £98.98

Buy the selected items together

Trade In this Item for up to £15.21
Trade in Essential Software Architecture for an Amazon Gift Card of up to £15.21, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Learn more

Product details

  • Hardcover: 260 pages
  • Publisher: Springer; 2nd ed. 2011 edition (6 May 2011)
  • Language: English
  • ISBN-10: 3642191754
  • ISBN-13: 978-3642191756
  • Product Dimensions: 23.4 x 15.7 x 2.3 cm
  • Average Customer Review: 3.5 out of 5 stars  See all reviews (2 customer reviews)
  • Amazon Bestsellers Rank: 692,921 in Books (See Top 100 in Books)
  • See Complete Table of Contents

Product Description


From the reviews of the second edition:

Choice - Oustanding Academic Title in 2012

“The volume is organized in three main parts, the first of which provides a comprehensive but clear definition of software architecture. The second and third parts are devoted to current and emerging practices, respectively. … This book will be of great help to students of computer science or software engineering, but above all it will provide practitioners with a guide to architecture that they can adopt to help direct their careers and professional development. Summing Up: Highly recommended. Upper-division undergraduates and above.” (L. Benedicenti, Choice, Vol. 49 (5), January, 2012)

“A subset of the software system architecture discipline is discussed in this book. … Gorton begins with an overall description of what he calls ‘the subdiscipline known as software architecture.’ … useful in the technical library of a large financial institution for those engaged in major systems development and evolution.” (Mordechai Ben-Menachem, ACM Computing Reviews, January, 2012)

From the Back Cover

Job titles like “Technical Architect” and “Chief Architect” nowadays abound in software industry, yet many people suspect that “architecture” is one of the most overused and least understood terms in professional software development.

Gorton’s book tries to resolve this dilemma. It concisely describes the essential elements of knowledge and key skills required to be a software architect. The explanations encompass the essentials of architecture thinking, practices, and supporting technologies. They range from a general understanding of structure and quality attributes through technical issues like middleware components and service-oriented architectures to recent technologies like model-driven architecture, software product lines, aspect-oriented design, and the Semantic Web, which will presumably influence future software systems. This second edition contains new material covering enterprise architecture, agile development, enterprise service bus technologies, RESTful Web services, and a case study on how to use the MeDICi integration framework.

All approaches are illustrated by an ongoing real-world example. So if you work as an architect or senior designer (or want to someday), or if you are a student in software engineering, here is a valuable and yet approachable knowledge source for you.

Inside This Book (Learn More)
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index
Search inside this book:

Customer Reviews

3.5 out of 5 stars
5 star
4 star
3 star
2 star
1 star
See both customer reviews
Share your thoughts with other customers

Most Helpful Customer Reviews

By Alex Ireland on 24 Jun. 2012
Format: Hardcover Verified Purchase
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.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
0 of 1 people found the following review helpful By Mr. Zebedee W. T. Mason on 11 Aug. 2012
Format: Hardcover Verified Purchase
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.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Most Helpful Customer Reviews on (beta) 1 review
A nice reference for the SW architect 15 July 2013
By Kratos_86 - Published on
Format: Hardcover Verified Purchase
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.
Was this review helpful? Let us know