Aaron B. Brown

TL;DR: Building systems to recover fast may be more productive than aiming for systems that never fail, and the authors advocate multiple lines of defense in managing failures.

TL;DR: The methodology uses fault injection to provoke situations where availability may be compromised, leverages existing performance benchmarks for workload generation and data collection, and can produce results in both detail-rich graphical presentations or in distilled numerical summaries.

TL;DR: There is a fundamental mismatch between traditional high-availability approaches—fault-tolerant hardware, careful software testing, vendor-supplied technicians—and the realities of modern heterogeneous, distributed server environments, like those backing e-commerce and e-business sites.

TL;DR: A model of configuration complexity is developed that represents systems as a set of nested containers with configuration controls and derives various metrics that indicate configuration complexity, including execution complexity, parameter complexity, and memory complexity.