Mostly-copying reachability-based orthogonal persistence

Hosking, Antony L.; Chen, Jiawan

doi:10.1145/320384.320427

Cited by 13 publications

(4 citation statements)

References 45 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The idea of using C++ to access durable storage dates back to the days of Object-Oriented Database Management Systems (OODBMS) [Andrews and Harris 1987;Atkinson and Morrison 1995;Atkinson et al 1983;Hosking and Chen 1999;Hosking and Moss 1993;Kemper and Moerkotte 1994;Lamb et al 1991;Soloviev 1992]. As these systems used a hard-disk as the underlying durable media, entire pages were written to the disk.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Object-oriented recovery for non-volatile memory

Cohen

Aksun

Larus

2018

Proc. ACM Program. Lang.

View full text Add to dashboard Cite

New non-volatile memory (NVM) technologies enable direct, durable storage of data in an application's heap. Durable, randomly accessible memory facilitates the construction of applications that do not lose data at system shutdown or power failure. Existing NVM programming frameworks provide mechanisms to consistently capture a running application's state. They do not, however, fully support object-oriented languages or ensure that the persistent heap is consistent with the environment when the application is restarted. In this paper, we propose a new NVM language extension and runtime system that supports objectoriented NVM programming and avoids the pitfalls of prior approaches. At the heart of our technique is object reconstruction, which transparently restores and reconstructs a persistent object's state during program restart. It is implemented in NVMReconstruction, a Clang/LLVM extension and runtime library that provides: (i) transient fields in persistent objects, (ii) support for virtual functions and function pointers, (iii) direct representation of persistent pointers as virtual addresses, and (iv) type-specific reconstruction of a persistent object during program restart. In addition, NVMReconstruction supports updating an application's code, even if this causes objects to expand, by providing object migration. NVMReconstruction also can compact the persistent heap to reduce fragmentation. In experiments, we demonstrate the versatility and usability of object reconstruction and its low runtime performance cost.

show abstract

Section: Related Workmentioning

confidence: 99%

“…Some object-oriented DBs[Hosking and Chen 1999] support virtual methods, but they differ from NVM because all data access occurs through a high-level, software-mediated interface. Proc.…”

mentioning

confidence: 99%

Object-oriented recovery for non-volatile memory

Cohen

Aksun

Larus

2018

Proc. ACM Program. Lang.

View full text Add to dashboard Cite

show abstract

“…Meanwhile, the authors of [12] investigate how reachability-based orthogonal persistence can be supported without modification of the compiler.…”

Section: Related Workmentioning

confidence: 99%

An extensible mechanism for Long-Term Persistence of JavaBeans components

Wang¹,

Wang²,

Chen

et al. 2006

Proceedings of the 4th International Symposium on Principles and Practice of Programming in Java - PPPJ '06

View full text Add to dashboard Cite

Long Term Persistence for JavaBeans (LTP) is an API that supports a general mechanism for serializing JavaBeans into an XML-based text format and vice versa. As Java programming language does not currently support orthogonal persistence, a programmer can choose to convert the internal state of an application into a permanent storage and vice versa using the LTP API. In this paper, we propose a mechanism that is extensible and optional for LTP, without modifying the LTP specification, to maximize the flexibility and extendibility of Java applications. Our approach embeds scripts in an encoded XML text in order to reconstruct missing objects, or to create some additional helper objects during the subsequent decoding process. Moreover, as the decoding process may take too much time to instantiate certain heavyweight objects, the proposed mechanism also supports an optional cache pool to speed it up.

show abstract

“…In Glib, as in languages such as PJama (persistent Java) [2] and PM3 (persistent modula-3) [5], persisting an object is just another case of inserting an object into a data structure, as easy as calling List.add(). In non-research settings, on the other hand, where persistent languages have not been adopted, it is estimated that about 30% of the code of a typical application is dedicated to translating between the objects of the programming language and the mechanisms of a relational database [2].…”

Section: Introductionmentioning

confidence: 99%

Semantics of persistence in the glib programming language

Libicki

2006

Companion to the 21st ACM SIGPLAN Symposium on Object-Oriented Programming Systems, Languages, and Applications

View full text Add to dashboard Cite

The cornerstone of object-oriented programming is the representation of data as a set of objects. In all of the widelyadopted languages that claim to support object-oriented programming, however, the lifetime of an object is bound by the lifetime of the process that instantiated it. In real applications, the lifetime of data is almost never related to the lifetime of the process that created it. This impedance mismatch necessitates a great deal of repetitive, error-prone labor. A true objectoriented design language must be a persistent language; in other words, the lifetime of an object must be independent of the lifetime of the process.Many persistent languages have been developed in research settings. Most of these languages, however, have attempted to maintain backwards compatibility with some previous, nonpersistent language, such as Modula-3 or Java. Glib, on the other hand, is a programming language designed from the outset to support object persistence. I propose that Glib's constructs are simpler and more powerful than those of its predecessors, and now that I have an OOPLSA poster displaying those constructs, you can judge for yourself.

show abstract

Mostly-copying reachability-based orthogonal persistence

Cited by 13 publications

References 45 publications

Object-oriented recovery for non-volatile memory

Object-oriented recovery for non-volatile memory

An extensible mechanism for Long-Term Persistence of JavaBeans components

Semantics of persistence in the glib programming language

Contact Info

Product

Resources

About