Speaking about ICT systems, especially safety-critical and real-time ones, we
might think about the implementation of resilience from the system level down
through to hardware and systems software. In addition, we need to consider that
each of the parts will both interact with and support each other.
Non-Functional Requirements (NFRs) of each part of the system were considered, such as:
– Performance;
– Reliability;
– Efficiency (mostly energy efficient).
Therefore, the systems that we design should be PRE-smart and provide these
properties throughout the life cycle.
Neither our books to date—have appeared as complete. These books have been
used in China, Switzerland, Russia, and USA (mostly Masters and Ph.D. students),
and we have received substantial feedback, such as:
• While reliability of hardware and availability at the system level are explained
and fine, there are no sections, or chapters about performance, especially where
parallel and distributed systems are concerned;
• How to apply (as mentioned in the above review) the classification and properties of resilience for and within distributed systems;
• How real-time and safety-critical applications should be treated considering the
system resilience: rules for system and for packages—have they changed?
It was especially satisfying when we discovered that these segments are being
updated by researchers around the globe, providing excellent contributions to the
content.
Thus, our book became an evolving system in itself, aggregating our further
efforts with the efforts and results of our colleagues from China, Switzerland, UK,
and Russia. Our book has therefore become itself resilient, benefiting from the
contributions from the following:
Performance chapter (including element-level performance and parallel design)
was prepared and included using materials and having contributions from:
– Professor Hao Kai, Shantou University, China;
– Simon Monkman, IT-ACS Ltd researcher.
System software chapters were part of substantial efforts from:
– Professor Eugeny Zuev and his team in Technopolis, Kazan, Russia.
In turn, requested in 1989 consideration of system level of resilience for distributed systems were developed as two chapters: system level and algorithmic
implementation prepared by me and Stephen Farrell. In these chapters, we have
introduced a concept of desperation (for transactions within distributed systems)
and show that our existing and new results, even patented: https://www.ipo.gov.uk/
p-ipsum/Case/PublicationNumber/GB2448351 can be extremely useful making the
viii
Introduction for Second Edition
might think about the implementation of resilience from the system level down
through to hardware and systems software. In addition, we need to consider that
each of the parts will both interact with and support each other.
Non-Functional Requirements (NFRs) of each part of the system were considered, such as:
– Performance;
– Reliability;
– Efficiency (mostly energy efficient).
Therefore, the systems that we design should be PRE-smart and provide these
properties throughout the life cycle.
Neither our books to date—have appeared as complete. These books have been
used in China, Switzerland, Russia, and USA (mostly Masters and Ph.D. students),
and we have received substantial feedback, such as:
• While reliability of hardware and availability at the system level are explained
and fine, there are no sections, or chapters about performance, especially where
parallel and distributed systems are concerned;
• How to apply (as mentioned in the above review) the classification and properties of resilience for and within distributed systems;
• How real-time and safety-critical applications should be treated considering the
system resilience: rules for system and for packages—have they changed?
It was especially satisfying when we discovered that these segments are being
updated by researchers around the globe, providing excellent contributions to the
content.
Thus, our book became an evolving system in itself, aggregating our further
efforts with the efforts and results of our colleagues from China, Switzerland, UK,
and Russia. Our book has therefore become itself resilient, benefiting from the
contributions from the following:
Performance chapter (including element-level performance and parallel design)
was prepared and included using materials and having contributions from:
– Professor Hao Kai, Shantou University, China;
– Simon Monkman, IT-ACS Ltd researcher.
System software chapters were part of substantial efforts from:
– Professor Eugeny Zuev and his team in Technopolis, Kazan, Russia.
In turn, requested in 1989 consideration of system level of resilience for distributed systems were developed as two chapters: system level and algorithmic
implementation prepared by me and Stephen Farrell. In these chapters, we have
introduced a concept of desperation (for transactions within distributed systems)
and show that our existing and new results, even patented: https://www.ipo.gov.uk/
p-ipsum/Case/PublicationNumber/GB2448351 can be extremely useful making the
viii
Introduction for Second Edition