Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
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 author
OK
Patterns for Fault Tolerant Software 1st Edition
| Price | New from | Used from |
|
Hardcover
"Please retry" | $1,599.97 | — | $1,599.97 |
- Kindle
$70.00 Read with our free app - Hardcover
$1,599.971 Used from $1,599.97
This new title in Wiley’s prestigious Series in Software Design Patterns presents proven techniques to achieve patterns for fault tolerant software. This is a key reference for experts seeking to select a technique appropriate for a given system.
Readers are guided from concepts and terminology, through common principles and methods, to advanced techniques and practices in the development of software systems. References will provide access points to the key literature, including descriptions of exemplar applications of each technique.
Organized into a collection of software techniques, specific techniques can be easily found with sufficient detail to allow appropriate choices for the system being designed.
- ISBN-100470319798
- ISBN-13978-0470319796
- Edition1st
- PublisherWiley
- Publication date
2007
November 28
- Language
EN
English
- Dimensions
7.8 x 1.0 x 9.6
inches
- Length
308
Pages
Editorial Reviews
From the Back Cover
Robert Hanmer, a Consulting Member of Technical Staff at Alcatel-Lucent, focuses on the software structures and mechanisms that can be designed into a system to enable its continued operation, even though a different part isn't working correctly.
Aimed at the novice as well as the experienced practitioner, the books ultimate goals is to provide you with proven techniques - in the form of patterns - to make programs less failure-prone when executing. The patterns included are divided into different groupings reflecting four main phases of fault tolerance:
-
Error Detection
-
Error Processing that consist of Error Recovery
-
Error Mitigation
-
Fault Treatment
as well as Architectural patterns that span these four phases.
Readers are guided from concepts and terminology, through common principles and methods, to advanced techniques and practices in the development of software systems. References provide access points to the key literature.
Patterns for Fault Tolerant Software provides you with a toolbox of techniques to build the fault tolerant patterns language needed to solve unique design problems.
Product details
- Publisher : Wiley; 1st edition (November 28, 2007)
- Language : English
- Hardcover : 308 pages
- ISBN-10 : 0470319798
- ISBN-13 : 978-0470319796
- Item Weight : 1.78 pounds
- Dimensions : 7.75 x 0.95 x 9.55 inches
- Best Sellers Rank: #4,406,853 in Books (See Top 100 in Books)
- #463 in Object-Oriented Software Design
- #1,179 in Computer Hardware Design & Architecture
- #2,085 in Object-Oriented Design
- Customer Reviews:
Important information
To report an issue with this product, click here.
About the author

Robert Hanmer has been working with patterns since the mid-1990s and doing software development even longer. He started out working on computer graphics -- “pre-teapot”. In the late 1980’s he switched to working on highly available systems for the telephone network. He’s written two books and has authored or co-authored 14 journal articles and several book chapters.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
We have begun using the book in an agile Community of Practice, at first to explain a couple of key ideas, and then more or less in "book club" discussions. It serves very well to raise the level of practice in a way that cuts through disagreements over details, and it has established a common vocabulary even among those who came with no experience with or interest in software patterns.
All in all, it is one of the most useful books on my bookshelf at work.
The pattern description is short but understandable, therefor its a very good source to get an overview about the topic.
Reading this book is definetly worth your time if you aim for building highly robust software.
Users and software are tied together, and the patterns often involve humans. Anyone who's been around fault-tolerant software design (or worked with software for a while) will recognize all the patterns. It's great to have names for them and allow them to be linked together, which is really a reason for a pattern language.
I would have given 5 stars to this if the Kindle version were smarter, i.e., it provided the following:
* Hyperlinks for every reference to patterns within the text. For example, you'll find ERROR HANDLER (30) cited multiple times, but there is no automatic linking to that portion of the book. Software scripts run on the source code of this book could identify and fix these links in no time at all. E-publishers should include this in the next version.
* The same could be said for bibliographic links, e.g., [2].
* The index of the book is useless (it has no hyperlinks whatsoever, and since kindle doesn't have page numbers, they aren't there either). I can understand it's a tougher problem to solve, but that's what computers and software are for! Other e-books do this right, so why not this one? Granted, "search" in Kindle works, but is not as useful as an author's intentional index.
* Some tables are represented as figures (images) and not text, so they don't scale and are not searchable. E.g., Figure 21.
* Erratum: RFC 2778 is referred to as RFC 2278.
Each week the students prepared a section or a group of patterns and explained and discussed the patterns as a group in front of other student groups that had to prepare other pattern books. Not only the students actually reading Bob's book, but also the students from the other groups got a great overview on the domain of fault tolerance. They often could relate the patterns from the book to their own experience and knowledge gained in other courses, i.e., on computer networks, and thus strengthen their understanding in both areas.
From a pattern perspective, I liked the "Alexandrian" approach as performed by Bob Hanmer very much, because in contrast to my own pattern writing style it suits better for "smaller" and interconnected patterns forming a pattern language. The pictures and visuals help a lot in memorizing and understanding the concepts behind the individual patterns.
The patterns are well explain and makes them feel 'obvious'. It doesn't feel like the patterns are more complicated than they need to be and the bare minimum.
Another good thing, the book is abstract, mostly not related to a concrete technology. That means it doesn't feel outdated immediately or only relevant for a certain technology. Despite the abstractness of the content, it can be applied to concrete software and never feels like 'PowerPoint-Architecture-Driven'
Top reviews from other countries
Natürlich hört man den Unterschied zwischen Fault / Error / Failure auf der Uni mal so nebenbei - nach dem Lesen des Buches versteht man aber auch warum die Separierung der Begriffe so essentiell ist. Das Buch covered die großen Themen Architekturgestaltung, Erkennen und Recovery von Fehlern und ein tolles Kapitel über Überlast / Zuverlässigkeit (Timingprobleme) und Datenprobleme. Man muss hier und da etwas viel blättern, da die Patterns sehr hierarchisch aufgebaut sind und daher viele Querverweise vorhanden sind - das beeinträchtigt den Lesespaß aber nicht sonderlich ...
Tolles Buch - leider erst spät entdeckt ...
Auch interessant - vom Autor des Buchs:
[...]
[...]