3 Evaluation of downtime risks
Assessing risks of unavailability allows quantifying the availability of a software solution. This assessment is necessary within the framework of the analysis because it allows comparing a software solution before and after putting in place methods to increase availability. This is done by adapting the work of Tsai and Sang , in section Method of calculating availability.
Contents · 15/26
- Design for High Availability
- Introduction
- 1 Hardware Abstraction
- 1.1 Isolating the levels of abstraction
- 1.2 Physical components category
- 1.3 Virtual Layer
- 1.4 Abstraction of virtual components
- 1.5 Characteristics of virtual components
- 2 High Availability Mecanisms
- 2.1 Framework for analysis of the mechanisms and assumptions
- 2.2 Public interface of a solution
- 2.3 Risk Control
- 2.4 One approach: duplication
- 2.5 Limits of replication of immutable virtual components
- 3 Evaluation of downtime risks
- 3.1 Dependency hierarchy
- 3.2 Bottlenecks
- 3.3 Method for calculating availability
- 3.4 Methodology of analysis
- 4 Evaluation in real cases
- 4.1 Basic software solution
- 4.2 Analysis without assumptions
- 4.3 Evaluation with addition of availability assumptions
- 4.4 Assumption in a cloud scenario
- Conclusion
- References