Implementing recoverable requests using queues
SIGMOD '90 Proceedings of the 1990 ACM SIGMOD international conference on Management of data
ACM Transactions on Database Systems (TODS)
Efficient transparent application recovery in client-server information systems
SIGMOD '98 Proceedings of the 1998 ACM SIGMOD international conference on Management of data
Logical logging to extend recovery to new domains
SIGMOD '99 Proceedings of the 1999 ACM SIGMOD international conference on Management of data
Phoenix: making applications robust
SIGMOD '99 Proceedings of the 1999 ACM SIGMOD international conference on Management of data
Transaction Processing: Concepts and Techniques
Transaction Processing: Concepts and Techniques
Persistent Applications Using Generalized Redo Recovery
ICDE '98 Proceedings of the Fourteenth International Conference on Data Engineering
Measuring and Optimizing a System for Persistent Database Sessions
Proceedings of the 17th International Conference on Data Engineering
Recovery Guarantees for General Multi-Tier Applications
ICDE '02 Proceedings of the 18th International Conference on Data Engineering
Highly available, fault-tolerant, parallel dataflows
SIGMOD '04 Proceedings of the 2004 ACM SIGMOD international conference on Management of data
Middleware-based database replication: the gaps between theory and practice
Proceedings of the 2008 ACM SIGMOD international conference on Management of data
Dependability, Abstraction, and Programming
DASFAA '09 Proceedings of the 14th International Conference on Database Systems for Advanced Applications
Event-driven replication in distributed systems
Proceedings of the 4th India Software Engineering Conference
Hi-index | 0.00 |
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.