// Workers AI · dad joke modeWhat did crash-only software say? It had a smashing time.
 | This article needs more citations. (August 2013) |
A crash-only software is a computer program that handle failures by simply restarting, without attempting any sophisticated recovery.[1] Correctly written components of crash-only software can microreboot to a known-good state without the help of a user. A related recovery technique is the microreboot, which restarts only a faulty fine-grained component rather than rebooting the whole application or server; in an Internet auction application, Candea et al. reported that microreboots recovered most of the same failures as full reboots while reducing recovery time and lost work by about an order of magnitude.[2] Since failure-handling and normal startup use the same methods, this can increase the chance that bugs in failure-handling code will be noticed,[clarification needed] except when there are leftover artifacts, such as data corruption from a severe failure, that don't occur during normal startup.[citation needed]
Crash-only software also has benefits for end-users. All too often, applications do not save their data and settings while running, only at the end of their use. For example, word processors usually save settings when they are closed. A crash-only application is designed to save all changed user settings soon after they are changed, so that the persistent state matches that of the running machine. No matter how an application terminates (be it a clean close or the sudden failure of a laptop battery), the state will persist.
See also
[edit]- Autosave – Automatic saving function
- End-to-end principle – Design principle for computer networking
- Erlang (programming language) § "Let it crash" coding style
References
[edit]- ↑ Candea, George; Fox, Armando (May 2003). "Crash-only software". 9th Workshop on Hot Topics in Operating Systems. Lihue, Hawaii, USA.
- ↑ Candea, George; Kawamoto, Shinichi; Fujiki, Yuichi; Friedman, Greg; Fox, Armando (2004). Microreboot—A Technique for Cheap Recovery. 6th Symposium on Operating Systems Design and Implementation (OSDI 04). San Francisco, California: USENIX Association.
External links
[edit]
 | This software-engineering-related article is a stub. You can help Wikipedia by adding missing information. |