English
 
Help Privacy Policy Disclaimer
  Advanced SearchBrowse

Item

ITEM ACTIONSEXPORT

Released

Journal Article

Recovery Guarantees for Internet Applications

MPS-Authors
/persons/resource/persons45468

Shegalov,  German
Databases and Information Systems, MPI for Informatics, Max Planck Society;

/persons/resource/persons45720

Weikum,  Gerhard
Databases and Information Systems, MPI for Informatics, Max Planck Society;

External Resource
No external resources are shared
Fulltext (restricted access)
There are currently no full texts shared for your IP range.
Fulltext (public)
There are no public fulltexts stored in PuRe
Supplementary Material (public)
There is no public supplementary material available
Citation

Barga, R., Lomet, D., Shegalov, G., & Weikum, G. (2004). Recovery Guarantees for Internet Applications. ACM Transactions on Internet Technology, 4, 289-328.


Cite as: https://hdl.handle.net/11858/00-001M-0000-000F-2B1A-D
Abstract
Internet-based e-services require application developers to deal explicitly with failures of the underlying software components, e.g. web servers, servlets, browser sessions, etc. This complicates application programming, and may expose failures to end users. This paper presents a framework for an applicationindependent infrastructure that provides recovery guarantees and masks almost all system failures, thus relieving the application programmer from having to deal with these failures, e.g. by making applications stateless. The main concept is an interaction contract between two components regarding message and state preservation. The framework provides comprehensive recovery encompassing data, messages, and the states of application components. We describe techniques to reduce logging cost, allow effective log truncation, and permit independent recovery for critical components. We illustrate the framework's utility via web-based eservices scenarios. Its feasibility is demonstrated by our prototype implementation of interaction contracts based on the Apache web server and the PHP servlet engine. Finally, we discuss industrial relevance for middleware architectures such as .Net or J2EE.