What do you think?
Rate this book
Designing Software Architectures
Brand New International Paper-back Edition Same as per description, **Economy edition, May have been printed in Asia with cover stating Not for sale in US. Legal to use despite any disclaimer on cover. Save Money. Contact us for any queries. Best Customer Support! All Orders shipped with Tracking Number
340 pages, Paperback
Published March 17, 2017
52 people are currently reading
452 people want to read
About the author
Miguel de Cervantes Saavedra
4,815 books3,525 followersMiguel de Cervantes y Cortinas, later Saavedra was a Spanish novelist, poet, and playwright. His novel Don Quixote is often considered his magnum opus, as well as the first modern novel.
It is assumed that Miguel de Cervantes was born in Alcalá de Henares. His father was Rodrigo de Cervantes, a surgeon of cordoban descent. Little is known of his mother Leonor de Cortinas, except that she was a native of Arganda del Rey.
In 1569, Cervantes moved to Italy, where he served as a valet to Giulio Acquaviva, a wealthy priest who was elevated to cardinal the next year. By then, Cervantes had enlisted as a soldier in a Spanish Navy infantry regiment and continued his military life until 1575, when he was captured by Algerian corsairs. He was then released on ransom from his captors by his parents and the Trinitarians, a Catholic religious order.
He subsequently returned to his family in Madrid.
In Esquivias (Province of Toledo), on 12 December 1584, he married the much younger Catalina de Salazar y Palacios (Toledo, Esquivias –, 31 October 1626), daughter of Fernando de Salazar y Vozmediano and Catalina de Palacios. Her uncle Alonso de Quesada y Salazar is said to have inspired the character of Don Quixote. During the next 20 years Cervantes led a nomadic existence, working as a purchasing agent for the Spanish Armada and as a tax collector. He suffered a bankruptcy and was imprisoned at least twice (1597 and 1602) for irregularities in his accounts. Between 1596 and 1600, he lived primarily in Seville. In 1606, Cervantes settled in Madrid, where he remained for the rest of his life.
Cervantes died in Madrid on April 23, 1616.
-Copied from Wikipedia
It is assumed that Miguel de Cervantes was born in Alcalá de Henares. His father was Rodrigo de Cervantes, a surgeon of cordoban descent. Little is known of his mother Leonor de Cortinas, except that she was a native of Arganda del Rey.
In 1569, Cervantes moved to Italy, where he served as a valet to Giulio Acquaviva, a wealthy priest who was elevated to cardinal the next year. By then, Cervantes had enlisted as a soldier in a Spanish Navy infantry regiment and continued his military life until 1575, when he was captured by Algerian corsairs. He was then released on ransom from his captors by his parents and the Trinitarians, a Catholic religious order.
He subsequently returned to his family in Madrid.
In Esquivias (Province of Toledo), on 12 December 1584, he married the much younger Catalina de Salazar y Palacios (Toledo, Esquivias –, 31 October 1626), daughter of Fernando de Salazar y Vozmediano and Catalina de Palacios. Her uncle Alonso de Quesada y Salazar is said to have inspired the character of Don Quixote. During the next 20 years Cervantes led a nomadic existence, working as a purchasing agent for the Spanish Armada and as a tax collector. He suffered a bankruptcy and was imprisoned at least twice (1597 and 1602) for irregularities in his accounts. Between 1596 and 1600, he lived primarily in Seville. In 1606, Cervantes settled in Madrid, where he remained for the rest of his life.
Cervantes died in Madrid on April 23, 1616.
-Copied from Wikipedia
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 7 of 7 reviews
August 14, 2022
Як на книжку по архітектурі, читається дуже легко і зрозуміло. Багато корисних посилань. Проте приклади, приведені в книзі та частина матеріалу застаріла, через що трохи дисонує. Але як теоретияна методичка буде корисна
August 19, 2021
There's little meat and a lot of repetitive fat to the content. Main takeaway is the ADD 3.0 methodology described in chapter 3 and used throughout the book in case studies, some alternative methods in chapter 7 and then an incredibly helpful appendix for identifying tactics based approaches (ex. Heartbeat, ping/echo, degradation, etc to help with availability concerns.)
Seriously, if the book was just chapters 3, 7 and the appendix it'd be a 5/5. If you're not a seasoned dev it's possible you may glean slightly more information if you can force yourself through the mundane parts.
The references after each chapter, however, sets this book on another level. An absolute superb job of providing additional reading. Without this I'd have given it a lower rating.
Seriously, if the book was just chapters 3, 7 and the appendix it'd be a 5/5. If you're not a seasoned dev it's possible you may glean slightly more information if you can force yourself through the mundane parts.
The references after each chapter, however, sets this book on another level. An absolute superb job of providing additional reading. Without this I'd have given it a lower rating.
November 2, 2020
The presented use-cases and methodical approach really hammers home the concept of architectural drivers and focusing on requirements - although using software instead of paper for doing the work seems more reasonable and future proof.
November 4, 2021
A broad perspective on the methodologies that exist out there to design a system architecture. This book is very practical with plenty of references and even a few case studies. Interesting read overall.
October 30, 2018
Very practical
January 25, 2025
Being a software architect back in the early 2000, I fully appreciate the value of the book for professional practising in such a role. The author not only revealed how software architecture design is about but also the Attribute-Driven Design (ADD) method that can be used by architects in the design process, with emphasis on drivers in particular quality attributes. This includes making design decisions to support performance, availability, modifiability, security and integrability. Steps and artifacts in the Architecture Design Process chapter are explained with the ADD method included, for example the use of reference architecture and design concepts catalogue.
The author also used a separate chapter to cover API-Centric Design and how ADD is useful in the design of APIs. Three chapters I like include "Designing for Deployability", "Designing Cloud-Based Solutions" and "Technical Debt in Architecture Design", which are not usually singled out to be discussed in architecture books.
Two cases, "Hotel Pricing System" and "Digital Twin Platform" are included with their Business Case, System Requirements, Development and Operations Requirements. These are followed with iterations of an architectural design for each of cases using ADD method in the design process.
Readers have to note that ADD is not the method for actual software architecture but a means to help in design decisions. Selection of reference architecture and any bespoke changes to it is the architect's call subject to the usage and requirements of the system. In addition to those reference architectures used by the author, there are other notable reference architectures including Domain-Driven Design, Model-Driven Architecture, Component-Based Design, Service-Oriented Architecture, Event-Driven Architecture, Layered Architecture Design, Object-Oriented Design, Data-Centric Architecture Design, DevOps-Driven Design etc.
The author also used a separate chapter to cover API-Centric Design and how ADD is useful in the design of APIs. Three chapters I like include "Designing for Deployability", "Designing Cloud-Based Solutions" and "Technical Debt in Architecture Design", which are not usually singled out to be discussed in architecture books.
Two cases, "Hotel Pricing System" and "Digital Twin Platform" are included with their Business Case, System Requirements, Development and Operations Requirements. These are followed with iterations of an architectural design for each of cases using ADD method in the design process.
Readers have to note that ADD is not the method for actual software architecture but a means to help in design decisions. Selection of reference architecture and any bespoke changes to it is the architect's call subject to the usage and requirements of the system. In addition to those reference architectures used by the author, there are other notable reference architectures including Domain-Driven Design, Model-Driven Architecture, Component-Based Design, Service-Oriented Architecture, Event-Driven Architecture, Layered Architecture Design, Object-Oriented Design, Data-Centric Architecture Design, DevOps-Driven Design etc.
March 10, 2019
This book comprehensively explains the ADD method (Attribute Driven Design) of designing a software. It catalogues each technique and methodology so you can understand it better and it also provides schemas on how you can go through each build process.
Its not an easy read book but not hard to understand. I do not have a software engineer degree and I want to learn more about it so I read this book. If you are a software engineer and want to be better, this book can be of help.
Its not an easy read book but not hard to understand. I do not have a software engineer degree and I want to learn more about it so I read this book. If you are a software engineer and want to be better, this book can be of help.
Displaying 1 - 7 of 7 reviews