Shoring up persistent applications

Abstract

SHORE (Scalable Heterogeneous Object REpository) is a persistent object system under development at the University of Wisconsin. SHORE represents a merger of object-oriented database and file system technologies. In this paper we give the goals and motivation for SHORE, and describe how SHORE provides features of both technologies. We also describe some novel aspects of the SHORE architecture, including a symmetric peer-to-peer server architecture, server customization through an extensible value-added server facility, and support for scalability on multiprocessor systems. An initial version of SHORE is already operational, and we expect a release of Version 1 in mid-1994.

Making the best of a bad situation: Prioritized storage management in GEMS

“…Chord [19], Gnutella [16], and PAST are fully decentralized systems, contrasted with centralized systems like Postgres [20] and NFS [17] tend toward centralized control, all of which represent extremes on the diagram. Databases like SHORE [4] and Google [2] represent moderately centralized databases, likewise, PVFS [5] and Lustre [21] represent moderately centralized file systems. Giggle [6], OceanStore [18], and FARSITE [1] represent replica systems, object systems, and file systems that tend toward peer-to-peer characteristics.…”

Efficient continuous skyline computation

“…Our experimental platform is built on top of the SHORE storage manager [5], which provides support for R * -trees. We also implemented a quadtree indexing method in SHORE.…”

SaIL: A Spatial Index Library for Efficient Application Integration

“…Storage management and buffering decisions are differed to the client code, which can use the storage management facilities of the framework (or any other framework, like SHORE [8]) directly. The tree internally only needs to use the ISerializable and IStorageManager interfaces, simplifying substantially node storage issues.…”