Buy new:
$27.20$27.20
+ $6.00 Shipping & Import Fees Deposit.
Ships from: Amazon Sold by: EZECREATIVES
Buy used: $22.06

Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet or computer – no Kindle device required. Learn more
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera, scan the code below and download the Kindle app.


Follow the Authors
OK
97 Things Every Software Architect Should Know: Collective Wisdom from the Experts Paperback – March 3 2009
Amazon Price | New from | Used from |
Kindle Edition
"Please retry" | — | — |
- Kindle Edition
$17.59 Read with Our Free App - Paperback
$27.20
Enhance your purchase
In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects -- including Neal Ford, Michael Nygard, and Bill de hOra -- offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. Among the 97 principles in this book, you'll find useful advice such as:
- Don't Put Your Resume Ahead of the Requirements (Nitin Borwankar)
- Chances Are, Your Biggest Problem Isn't Technical (Mark Ramm)
- Communication Is King; Clarity and Leadership, Its Humble Servants (Mark Richards)
- Simplicity Before Generality, Use Before Reuse (Kevlin Henney)
- For the End User, the Interface Is the System (Vinayak Hegde)
- It's Never Too Early to Think About Performance (Rebecca Parsons)
To be successful as a software architect, you need to master both business and technology. This book tells you what top software architects think is important and how they approach a project. If you want to enhance your career, 97 Things Every Software Architect Should Know is essential reading.
- ISBN-10059652269X
- ISBN-13978-0596522698
- Edition1st
- PublisherO'Reilly Media
- Publication dateMarch 3 2009
- LanguageEnglish
- Dimensions15.24 x 1.35 x 22.86 cm
- Print length222 pages
Frequently bought together
- +
- +
Customers who bought this item also bought
Product description
About the Author
Richard Monson-Haefel , an independent software developer, coauthored all five editions of Enterprise JavaBeans and Java Message Service (all O'Reilly). He's a software architect specializing in multi-touch interfaces and a leading expert on enterprise computing. More detail on his work and writings can be found at www.monson-haefel.com.
Product details
- Publisher : O'Reilly Media; 1st edition (March 3 2009)
- Language : English
- Paperback : 222 pages
- ISBN-10 : 059652269X
- ISBN-13 : 978-0596522698
- Item weight : 304 g
- Dimensions : 15.24 x 1.35 x 22.86 cm
- Best Sellers Rank: #669,138 in Books (See Top 100 in Books)
- #195 in Hardware Design & Architecture
- #636 in Software Design & Engineering Textbooks
- #2,115 in Software Architecture
- Customer Reviews:
About the authors
Discover more of the author’s books, see similar authors, read author blogs and more
I'm an independent consultant, international speaker, writer and trainer. I live in Bristol and online.
My software development interests are in patterns, programming, practice and process. As well as contributing to a number of projects, I've been involved in (far too) many committees (for conferences, publications and standards, but as yet I've not been on a committee for committees).
My fiction writing tends to the short side — and occasionally to the dark side — spanning a number of genres.
Customer reviews
-
Top reviews
Top reviews from Canada
There was a problem filtering reviews right now. Please try again later.
This makes it not only easy to read,but one can literally jump to any part of the book.
The context offered is from architects with real experience.
Interesting reading if you are already in the architect role and want a reminder of those things you should be doing, but you'll need to know the details behind the advice to really make use of it. Worthwhile if that's what you're looking for.
The format of the book is such that each entry takes up 2 pages. However, most entries only need close to 1 page, so much of the book is white space. On the plus side, it's very small and light to take with you on the bus.
If you like reading blog entries that are mostly opinion pieces about the topics around software architecture (including personal communication, teamwork, business challenges, etc.), this might be a really good fit for you. I found that too much of the content is simply common sense.
Of course, our industry isn't the best at always applying common sense, so perhaps some people might find this useful as a gift to their coworkers. I would choose to apply my personal time and money elsewhere.
Top reviews from other countries

That said, there are some really enjoyable bits and pieces. My favourite parts:
* Keith Braithwaite's reminding of the architect's need to quantify things. Characteristics such as average response
time should be not be phrased using terms such as 'good' or 'satifactory' but quantified as something like:
'between 750ms and 1,250ms'
* Craig Russell's points about including the human interaction time in any performance analysis. The system
may respond very fast to API calls, but the if the UI is counter-intuitive, it means the user will spend a longer time try to
get his result.
* Michael Nygard advice for engineering the 'white spaces'. Don't just have arrows between components specifying the
communication protocol, describe the performance expectation of interaction e.g. 100 requests per second, response time
250ms 99% of time. Describe how the system will handle overload, bad response times, unavailability etc.
* Mark Richards classification of architectural patterns:
- Enterprise Architecture Patterns: EDA, SOA, ROA, Pipeline architecture
- Application Architecture: Session Facade, Transfer Object
- Integration Patterns: File sharing, RPC, Messaging
- Design Patterns: GoF
* Gregor Hohpe arguments about the 'predictive call-stack architecture' becoming a thing of the past.
In massive distributed systems, it's not so easy to define the order things happen in. Architectures now have
to be able to respond to event in any time order.
* Bill de hOra discussion of inevitable tradeoffs using Brewer's conjecture (CAP) as example.
* Dave Anderson's arguments for the inevitabitly of legacy and preparing your system for maintenance.
So plenty of good advise in a short book that never gets too technical. The role of the architect is not just to be understanding complicated problems but to stand back and look at the big picture, checking for gaps and to ensure the right actions are taken to ensure project success. This means it's not really just about things a software architect should know, but about things a software architect should ensure they do not forget.


il est essentiellement la compilation de plusieurs retours d'expériences de plusieurs architectes 'connus'.
je le conseille vivement.
