Editing Microreboot

'''Microrebooting''' is a technique used to recover from failures in [[crash-only software]] systems.  Instead of [[booting|rebooting]] the whole system, only subsets of fine-grain components are restarted.  The granularity of components is typically finer than the process level (e.g., [[EJB]]-level in [[Java EE]] systems).

The goal of confining the reboot to fine-grain components is threefold: to reduce the amount of time it takes for the system to return to service, to minimize the failure's disruption to the system and its users, and to preserve as much in-memory application data as possible.

The concept was proposed in 2001 by [[George Candea]] and [[Armando Fox]], while the former was a graduate student at [[Stanford University]].  It was initially reduced to practice in systems such as a satellite ground station control system and a Java EE [[application server]]; later on it formed the basis of the design of commercial systems like [[Aster Data Systems]] nCluster.<ref>{{cite news|last=Teradata Aster |title=A Childhood Dream |url=http://www.asterdata.com/blog/2008/10/12/a-childhood-dream/ |accessdate=7 Jan 2016 |url-status=unfit |archiveurl=https://web.archive.org/web/20110312035240/http://www.asterdata.com/blog/2008/10/12/a-childhood-dream/ |archivedate=March 12, 2011 }}</ref><ref>{{cite web|last=Fox |first=Armando |title=Recovery-Oriented Computing |url=http://www.armandofox.com/geek/past-projects/recovery-oriented-computing-roc/ |accessdate=7 Jan 2016 |url-status=unfit |archiveurl=https://web.archive.org/web/20130114154916/http://www.armandofox.com/geek/past-projects/recovery-oriented-computing-roc/ |archivedate=January 14, 2013 }}</ref>

==References==
{{Reflist}}

== Further reading ==
* [http://dslab.epfl.ch/pubs/microreboot.pdf Microreboot paper]
* [http://dslab.epfl.ch/pubs/recursive_restartability.pdf Recursive restartability paper]
* [http://dslab.epfl.ch/pubs/crashonly.pdf Crash-only software paper]

[[Category:Booting|Boot, Microreboot]]