Abstract:
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 recov-
ery. Crash-only systems are built from crash-only compo-
nents, 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 sys-
tems, showing that it can lead to more reliable, predictable
code and faster, more effective recovery. We present ideas
on how to build such crash-only Internet services, taking
successful techniques to their logical extreme.
No comments:
Post a Comment