Crash-Only Software

  title={Crash-Only Software},
  author={George Candea and Armando Fox},
Crash-only programs crash safely and recover quickly. There is only one way to stop such software—by crashing it—and only one way to bring it up—by initiating recovery. Crash-only systems are built from crash-only components, and the use of transparent component-level retries hides intra-system component crashes from end users. In this paper we advocate a crash-only design for Internet systems, showing that it can lead to more reliable, predictable code and faster, more effective recovery. We… CONTINUE READING
Highly Cited
This paper has 127 citations. REVIEW CITATIONS


Publications citing this paper.
Showing 1-10 of 89 extracted citations

Failure Semantics in a SOA Environment

2008 International MCETECH Conference on e-Technologies (mcetech 2008) • 2008
View 7 Excerpts
Highly Influenced

Guaranteed Physical Security with Restart-Based Design for Cyber-Physical Systems

2018 ACM/IEEE 9th International Conference on Cyber-Physical Systems (ICCPS) • 2018
View 1 Excerpt

127 Citations

Citations per Year
Semantic Scholar estimates that this publication has 127 citations based on the available data.

See our FAQ for additional information.


Publications referenced by this paper.
Showing 1-10 of 26 references

Decoupled storage: State with stateless-like properties

A. C. Huang, A. Fox
Submitted to the 22nd Symposium on Reliable Distributed Systems, • 2003
View 4 Excerpts
Highly Influenced

Application isolation API specification

P. Soper, P. Donald, D. Lea, M. Sabin
Java Specification Request No. 121,, • 2002
View 1 Excerpt

Personal communication

A. Pal
Yahoo!, Inc., • 2002
View 1 Excerpt

Similar Papers

Loading similar papers…