Persistent object store
This article provides insufficient context for those unfamiliar with the subject.Learn how and when to remove this template message)(September 2016) (
This article relies largely or entirely on a single source. (September 2016)
Contrasting Storage Methods
This is different from file storage, where a single file may hold multiple objects. For example, file with comma-separated values may hold many objects, generally one per line. The system has to open the file from the start and read through it to access an object in the middle. It is also different from block storage, which may break a single object up into smaller pieces for storage convenience.
Whereas files are modeled after linear human documents and data streams, object storage is primarily intended to support object-oriented programming languages. These languages will maintain their own volatile object store in memory, but when the program stops or needs to make room in memory, a persistent object store can hold the objects for reuse later or by another program. Writing the objects out is called data serialization.
Variations in Implementation
Simple examples store the serialized object in binary format (zeroes and ones). More complex examples include object databases or object-relational mapping systems, which combine a database system with support for easily storing objects. They may be serialized in private and obscure formats or in a widely portable formats such as XML or JSON.
The most important components of a persistent object store are:
- The identification of persistent objects
- The properties of objects and their interconnections
- The scale of the object store
- The provision of stability
|This computing article is a stub. You can help Wikipedia by expanding it.|