(Enter summary)
Abstract: 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 ... (Update)
Cited by: More
Highly-Available, Fault-Tolerant, Parallel Dataflows - Shah, Hellerstein, Brewer (2004)
(Correct)
Highly Available, Fault-Tolerant, Parallel Dataflows - Shah, Hellerstein, Brewer (2004)
(Correct)
Similar documents (at the sentence level):
11.1%: Phoenix: Making Applications Robust - Barga, Lomet (1999)
(Correct)
Active bibliography (related documents): More All
0.6: Measuring and Optimizing a System for Persistent Database.. - Barga, Lomet
(Correct)
0.5: A Lightweight and Scalable e-Transaction Protocol for.. - Romano, Quaglia, Ciciani
(Correct)
0.3: A Review of the Rationale and Architectures of PJama: a.. - Atkinson, Jordan (2000)
(Correct)
Similar documents based on text: More All
0.5: The Microsoft Database Research Group - Lomet, Barga, Chaudhuri, Larson..
(Correct)
0.4: Recovery Guarantees for Internet Applications - Roger Barga David
(Correct)
0.3: Data Engineering - June Vol No
(Correct)
Related documents from co-citation: More All
2: Implementing Recoverable Requests Using Queues (context) - Bernstein, Hsu et al. - 1990
2: NiagaraCQ: A scalable continuous query system for internet databases
- Chen, DeWitt et al. - 2000
2: A database system for real-time event aggregation in telecommunication
- Baulier, Blott et al. - 1998
BibTeX entry: (Update)
D. Lomet and R. Barga. Phoenix Project: Fault Tolerant Applications. SIGMOD Record, June 2002. http://citeseer.ist.psu.edu/article/lomet02phoenix.html More
@misc{ lomet02phoenix,
author = "D. Lomet and R. Barga",
title = "Phoenix Project: Fault Tolerant Applications",
text = "D. Lomet and R. Barga. Phoenix Project: Fault Tolerant Applications. SIGMOD
Record, June 2002.",
year = "2002",
url = "citeseer.ist.psu.edu/article/lomet02phoenix.html" }
Citations (may not include all citations):
901
Transaction Processing: Concepts and Techniques (context) - Gray, Reuter - 1993
189
ARIES: A transaction recovery method supporting fine-granula.. (context) - Mohan - 1992
180
A Survey of Rollback-Recovery Protocols in MessagePassing Sy..
- Elnozahy, Johnson et al. - 1996
48
Implementing Recoverable Requests Using Queues (context) - Bernstein, Hsu et al. - 1990
6
Efficient Transparent Application Recovery in Client-Server ..
- Lomet, Weikum - 1998
6
Logical Logging to Extend Recovery to New Domains
- Lomet, Tuttle - 1999
5
Phoenix: Making Applications Robust
- Barga, Lomet - 1999
4
Persistent Client-Server Database Sessions (context) - Barga, Lomet et al.
3
Persistent Applications Using Generalized Redo Recovery
- Lomet - 1998
2
Recovery Guarantees for Internet Applications
- Barga, Lomet et al.
1
Measuring and Optimizing a System for Persistent Database Se..
- Barga, Lomet
1
Principles of Redo Recovery (context) - Lomet, Tuttle
1
Recovery Guarantees for Multi-tier Applications (context) - Barga, Lomet et al. - 2002
www.zend.com
Documents on the same site (http://www.research.microsoft.com/~lomet/): More
Logical Logging to Extend Recovery to New Domains - David Lomet (1999)
(Correct)
High Speed On-line Backup When Using Logical Log Operations - Lomet
(Correct)
The BT-Tree: A Branched and Temporal Access Method - Jiang, Salzberg, Lomet (1999)
(Correct)
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC