3.2 Bottlenecks
Bottlenecks help identify the logic components most likely to have an adverse impact on the availability of a software solution. They can be defined as logic components whose availability has the most impact on the availability of other components of the solution. Contextual availability of each component then represents the impact of the availability of this component on the other components of the solution. When the contextual availability of each component is established, it can be compared with those of other components to find the bottlenecks. This then allows one to target components that have the most impact on the availability of the solution.
Contents · 17/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