GOAL OR METRIC: Zero Disruption in Service After Individual Component Failure
RATIONALE: The expectations of cloud-based computing are still at the point of "inflated expectations." But even for those organizations that are currently employing cloud computing (public, private, or hybrid), the expectations are high. Efficient organizations using cloud computing build just enough redundancy or failover to eliminate breaks in service after a component failure, but not so much that costs are inappropriate. Zero disruption in service is the mark of an organization that is using a strategy that balances reliability and performance with "just enough" redundancy.
POTENTIAL RESULTS: End users see no disruption in service and breaks in service are automatically remediated (no wasted staff time).
The term five 9's is used too often aka 99.999%. 90 percent is doable but that last 9.999% is expensive and management wants that last part at zero cost. The truth is that the exorbitant cost of maintaining a higher level of up-time goes up exponentially with each additional "9." For some it might not be necessary. It can also impractical for the limited resources $$$$$$$.