Availability is a should be classified as to the Data Security Impact
Improving maintainability is generally easier than reliability. Maintainability estimates (Repair rates) are also generally more accurate. However, because the uncertainties in the reliability estimates are in most cases very large, it is likely to dominate the availability (prediction uncertainty) problem, even while maintainability levels are very high.[1]
Availability implies there is a some level of Fault tolerance
Any project planning should include some statement of acceptable availability which directly influences design considerations.
This table shows the amount of time your service would be allowed to be un-avalable for each level of Availability.
Availability | Downtime/year | Downtime/month | Downtime/week | Downtime/day |
---|---|---|---|---|
98.0000% | 7.30 days | 14.4 hours | 3.360 hours | 28.80 minutes |
99.0000% | 3.65 days | 7.20 hours | 1.680 hours | 14.40 minutes |
99.5000% | 1.83 days | 3.60 hours | 50.40 minutes | 7.200 minutes |
99.9000% | 8.76 hours | 43.2 minutes | 10.10 minutes | 1.440 minutes |
99.9900% | 52.3 minutes | 4.32 minutes | 1.010 minutes | 8.660 seconds |
99.9990% | 5.26 minutes | 25.9 seconds | 6.050 seconds | 0.864 seconds |
99.9999% | 31.5 seconds | 2.59 seconds | 0.065 seconds | 0.009 seconds |
You should balance the risk vs rewards vs the costs for each level.