Fundamentals of Software Architecture: An Engineering Approach
Product ID: 163988773
Desertcart purchases this item on your behalf and handles shipping, customs, and support to India.
Salary surveys worldwide regularly place software architect in the top 10 best jobs, yet no real guide exists to help developers become architects. Until now. This book provides the first comprehensive overview of software architecture's many aspects. Aspiring and existing architects alike will examine architectural characteristics, architectural patterns, component determination, diagramming and presenting architecture, evolutionary architecture, and many other topics. Mark Richards and Neal Ford-hands-on practitioners who have taught software architecture classes professionally for years-focus on architecture principles that apply across all technology stacks. You'll explore software architecture in a modern light, taking into account all the innovations of the past decade. This book examines: Architecture patterns: The technical basis for many architectural decisions Components: Identification, coupling, cohesion, partitioning, and granularity Soft skills: Effective team management, meetings, negotiation, presentations, and more Modernity: Engineering practices and operational approaches that have changed radically in the past few years Architecture as an engineering discipline: Repeatable results, metrics, and concrete valuations that add rigor to software architecture Review: Better than expected! - I'm not sure if it's the fact that I got burned by Building Evolutionary Architectures, co-authored by Neal Ford, or my previous experience with other "fundamentals" books which tended to be rather useless - my expectations were fairly low of this one but I'm glad I went ahead and read it. The book starts off by discussing what software architecture is, what the job entails, what the common misconceptions are and then for the remainder of the book covers both the technical and soft skills required for a person to become a good architect - how to maintain the technical know-how required by the job, what types of knowledge to focus on, how to detect, discuss and document the architecture, the reasons behind it and the trade-offs it entails, how to interact with your colleagues, both on the developer and the business side, how to resolve conflicts, nurture and promote constructive collaboration etc. So, as you can see, the authors try to cover a lot of ground without going too deep (and waking Durin's Bane) - and they do it successfully. That being said, the book isn't perfect, some chapters could have used more feedback, especially the event-driven architecture one, which felt a bit dated and like it came from someone who didn't have firsthand experience with it recently. Also, I can't really say that I truly discovered something new within its pages - which isn't necessarily a bad thing if, like here, the summary of the things you know is presented in such a way it actually reinforces the existing knowledge. Review: Awesome Book! - I read this book as an Associate SE and I gained a ton of knowledge. This book is extremely well written. I enjoyed the order in which the topics were presented. It began with an explanation of the four pillars in software architecture. By doing so readers gain immediate value within the first few pages. I particularly enjoyed the advocation for a domain partitioned folder structure as opposed to a technically partitioned folder structure, especially for front end developers. I believe navigating the code base should very much resemble navigating the UI. This is not only cool for readability, but it inherently increases cohesion. A huge win for such a low cost. After getting the foundations laid the authors explain different architecture styles. The part I found to be most useful was the charts they provided which give star ratings to highlight the strength and weaknesses of each architecture. This illustrates that architecture styles should be chosen for specific solutions and not trends. I gained the skills necessary to begin to think like an architect. It included breadth of knowledge which, as the book will tell you, is much more important than depth of knowledge for an architect. Then the authors decided to dive back in and elaborate a bit more on the foundations learned at the beginning. It suggested ADRs, another quick win for low costs. They also spoke about risks storming and offered friendly advice on finding balance within the teams. All in all, an amazing book. And at the end, the authors even presented tons of short answer questions to challenge readers and really take the lesson home.
| Best Sellers Rank | #515,481 in Books ( See Top 100 in Books ) #5 in Software Design Tools #26 in Software Development (Books) #142 in Business Technology |
| Customer Reviews | 4.6 out of 5 stars 1,156 Reviews |
F**K
Better than expected!
I'm not sure if it's the fact that I got burned by Building Evolutionary Architectures, co-authored by Neal Ford, or my previous experience with other "fundamentals" books which tended to be rather useless - my expectations were fairly low of this one but I'm glad I went ahead and read it. The book starts off by discussing what software architecture is, what the job entails, what the common misconceptions are and then for the remainder of the book covers both the technical and soft skills required for a person to become a good architect - how to maintain the technical know-how required by the job, what types of knowledge to focus on, how to detect, discuss and document the architecture, the reasons behind it and the trade-offs it entails, how to interact with your colleagues, both on the developer and the business side, how to resolve conflicts, nurture and promote constructive collaboration etc. So, as you can see, the authors try to cover a lot of ground without going too deep (and waking Durin's Bane) - and they do it successfully. That being said, the book isn't perfect, some chapters could have used more feedback, especially the event-driven architecture one, which felt a bit dated and like it came from someone who didn't have firsthand experience with it recently. Also, I can't really say that I truly discovered something new within its pages - which isn't necessarily a bad thing if, like here, the summary of the things you know is presented in such a way it actually reinforces the existing knowledge.
M**K
Awesome Book!
I read this book as an Associate SE and I gained a ton of knowledge. This book is extremely well written. I enjoyed the order in which the topics were presented. It began with an explanation of the four pillars in software architecture. By doing so readers gain immediate value within the first few pages. I particularly enjoyed the advocation for a domain partitioned folder structure as opposed to a technically partitioned folder structure, especially for front end developers. I believe navigating the code base should very much resemble navigating the UI. This is not only cool for readability, but it inherently increases cohesion. A huge win for such a low cost. After getting the foundations laid the authors explain different architecture styles. The part I found to be most useful was the charts they provided which give star ratings to highlight the strength and weaknesses of each architecture. This illustrates that architecture styles should be chosen for specific solutions and not trends. I gained the skills necessary to begin to think like an architect. It included breadth of knowledge which, as the book will tell you, is much more important than depth of knowledge for an architect. Then the authors decided to dive back in and elaborate a bit more on the foundations learned at the beginning. It suggested ADRs, another quick win for low costs. They also spoke about risks storming and offered friendly advice on finding balance within the teams. All in all, an amazing book. And at the end, the authors even presented tons of short answer questions to challenge readers and really take the lesson home.
J**E
Kindle Ed: Seems like a good book, but online material leads to a 404. Some diagrams are unreadable
Preliminary review: a lot of the book's online material leads to a 404. I can't give 5 stars for that reason Some of the diagrams have text on them, and they are hard to read in the Kindle ed
S**U
Very good
Good book, perfect conditions
A**R
Excellent overview of different architectures
Excellent overview of different architectures and enable one to ask more questions, the right questions, and the right keywords to look up for further exploration and self study. There are no implementation details but a good idea of the structure, action, pros and cons. So this book won't teach you how to implement messaging or Domain Driven Design, for example, but will give you an idea about how to identify whether and where they are needed, and why. A solid step up for those who know how all the parts work and now would like to know, how to know, which parts will be appropriate in different situations.
K**R
a thorough window into the architect role
The book does a great job at deconstructing the overall role of a software architect in an enterprise scenario. It does this pretty gradual, starting with definitions for the characteristics of a software architecture and then elaborating clearly through architectural styles and skills that are favorablr in certain contexts. A definite must read for anyone looking to understand the abstractions involved in both software architecture at an enterprise level and the role of a software architect.
B**.
Covered the material well & leveled up my understanding
I read this book front to back and it solidified my understanding of a lot of architectural concepts. Now I'm better at understanding and communicating the architectural concerns of the systems I work on. If you're wondering where the blurry lines around architecture are, this book will help you build the mental model you're missing. Great writing, I'm keeping it as a reference book.
C**R
Must have
This book is a fundacional stone to anyone who’s beginning their architecture career. If you got the chance to buy it or read it just go for it every page is building block in your understanding on software architecture
K**I
Best basics for software.
I found this book to be the best at explaining software, to beginners, and a great refresher for those who have more experience.
S**.
Exzellent und up to date
Insbesondere das im zweiten Teil des Buchs herausgearbeitete Gesetz "the why is more important than the how" ist eine im Alltag immer wieder erlebte Erfahrung in Sachen Architektur und Source Code. Da dies häufig missachtet wird, kann die WTF Rate schnell ansteigen. Im ersten Teil des Buchs werden diverse Architekturvarianten vorgestellt, bewertet und Empfehlungen für Anwendungsfälle gegeben. Klasse Hilfsmittel. Wichtigste Regel: Es gibt keine Silver Bullets sonder immer nur die am wenigsten schlechte Lösung. Es wurde bemängelt, dass die Qualität der Diagramme und Grafiken im gedruckten Buch sehr schlecht ist. Das stimmt, aber es gibt eine zum Buch gehörende Website, auf der die Diagramme in hoher Auflösung verfügbar sind. Einfach ohne voranstehendes www die com Domain fundamentalsofsoftwarearchitecture aufrufen und die Sektion Updated Images anwählen. Klare Kaufempfehlung!
L**A
Mark Richards una garanzia!
L’autore tratta in maniera eccellente le architetture software a 360 gradi, il libro è utile sia per chi si approccia per la prima volta in questo ambito sia per chi vuole approfondire.
S**M
Interesting book
Very nice book. I highly recommend it
A**N
Diagrams unreadable
Most diagrams, which are an important part of the book, are completely unreadable. This is really a shame for otherwise good quality content.
Trustpilot
2 weeks ago
3 weeks ago