Roger Barga and David Lomet
After a system crash, databases recover to the
last committed transaction, but applications
usually either crash or cannot continue. The
Phoenix purpose is to enable application state to
persist across system crashes, transparent to the
application program. This simplifies application
programming, reduces operational costs, masks
failures from users, and increases application
availability, which is critical in many scenarios,
e.g., e-commerce. Within the Phoenix project,
we have explored how to provide application
recovery efficiently and transparently via redo
logging. This paper describes the conceptual
framework for the Phoenix project, and the
software infrastructure that we are building.
In SIGMOD Record
Publisher Association for Computing Machinery, Inc.
Copyright © 2007 by the Association for Computing Machinery, Inc. Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, to republish, to post on servers, or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from Publications Dept, ACM Inc., fax +1 (212) 869-0481, or firstname.lastname@example.org. The definitive version of this paper can be found at ACM’s Digital Library --http://www.acm.org/dl/.