December 2007
Intermediate to advanced
309 pages
7h 20m
English
Content preview from Patterns for Fault Tolerant Software
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Appendix A. Appendices
Patterns for Fault Tolerant Software Thumbnails
Table A.1. Patterns for fault tolerant software
Pattern | Pattern Intent |
|---|---|
Acknowledgement (17) | Send a reply message to let a communicating party know that that the sender is alive. |
Checkpoint (37) | Save state periodically so that it does not need to be regenerated from the beginning of execution |
Checksum (25) | Add information to data or messages to verify that they are correct. |
Complete Parameter Checking (14) | Check all the inputs and parameters rigorously to prevent bad results from causing errors during execution. |
Concentrated Recovery (29) | The system should have as few distractions as possible during error recovery. |
Correcting Audits | Design data to be checked and check data for errors. If errors are found, correct both the erroneous data and look for errors in related data. |
Data Reset (41) | Restore some data to its initial (or a predetermined) value when it is found incorrect. |
Deferrable work (43) | A system that is performing well in an overload situation does not need to be fixed by Routine Maintenance (22). |
Equitable Resource Allocation (45) | Divide the resources up equitably between all the requestors. |
Error Containment Barrier (13) | Isolate errors so that they do not spread. |
Error Correcting Codes (57) | Add redundant information to data so that errors can be detected as in Checksum (25) and also automatically corrected. |
Error Handler (30) | Provide a controlled manner for handling errors. |
Escalation (9) | When error processing steps are not producing ... |
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.