Fundamentals of Software Architecture: An Engineering Approach
£48.54£55.99 (-13%)
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
Read more
Additional information
| Publisher | O′Reilly (7 Feb. 2020) |
|---|---|
| Language | English |
| Paperback | 400 pages |
| ISBN-10 | 1492043451 |
| ISBN-13 | 978-1492043454 |
| Dimensions | 17.78 x 2.18 x 23.34 cm |
by Dimitrios K. Mistriotis
Last book I buy from O’Reilly.
The review has nothing to do with the content but with the quality of the book. A friend gave me a PDF version, read it a bit, the content was amazing which made me want to purchase. From the colors inside the book plus price thought there would be something similar to recent Manning publications: high-quality paper and nice graphs. Well… no.
Paper is photocopy quality, everything black and white, graphs have not been adjusted to black and white which makes some unreadable. Again, assumed it would not have been the case because of the very high price.
Will make notes with pens + highlighters which is why I prefer printed books, while this is also my last O’Reilly purchase.
by Just Some Guy
This is a great book – but it’s not what I expected, or what I was really looking for. In short, *spoiler alert* – the constant theme of this book is “There are no clear right or wrong answers, there are only tradeoffs.” That advice gets repeated in every chapter of the book, through countless examples.
That’s terrific practical advice, and good knowledge for any architect to have. However, if you’re looking for a book full of design patterns and specific advice about how best to implement something, you will be very frustrated by this book. In fact, there’s essentially zero actual code in the entire book. It’s not that kind of book.
The first 2/3 of the book do outline a lot of broad architectural styles and patterns, and do an excellent job of considering the many pros and cons of each. The last section of the book, though, is entirely about “soft skills” career advice for effectively doing the *job* of architect in a company (people skills, management skills, presentation skills, etc.). Frankly, the title doesn’t imply that at all, and I just wish this book had been called something more accurate to its true nature, like: “How to Pursue a Software Architect Career”
by A. Rose
This is a well thought out book that acts as a useful reference. It covers a mixture of patterns and working practices do is more about breadth than depth.
I originally purchased the audio book but liked this enough 5o purchase the paper version as well
by PerivaleElvis
The structure of this book is excellent. It gives the reader an excellent lesson in what the elusive thing called architecture is really all about and creates a great distinction between architecture and design. It also has great references to other material if you require more depth. I’d strongly recommend this book to anybody involved in creating complex IT solutions.