Microrebooting is a technique used to recover from failures in

crash-only software Crash-only software refers to computer programs that handle failures by simply restarting, without attempting any sophisticated recovery. Correctly written components of crash-only software can microreboot to a known-good state without the help ...

systems. Instead of 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 Jakarta Enterprise Beans (EJB; formerly Enterprise JavaBeans) is one of several Java APIs for modular construction of enterprise software. EJB is a server-side software component that encapsulates business logic of an application. An EJB ...

-level in

Java EE Jakarta EE, formerly Java Platform, Enterprise Edition (Java EE) and Java 2 Platform, Enterprise Edition (J2EE), is a set of specifications, extending Java SE with specifications for enterprise features such as distributed computing and web se ...

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 Aster Data Systems was a data management and analysis software company headquartered in San Carlos, California. It was founded in 2005 and acquired by Teradata in 2011. History Aster Data was co-founded in 2005 by Stanford University graduate st ...

nCluster.

References

{{Reflist

References

Further reading