Perst

Perst
Developer(s) McObject
Operating system Cross-platform
Type ODBMS
License GPL or Commercial License
Website www.mcobject.com/perst

Perst is an open source, dual license, object-oriented embedded database management system (ODBMS), available in two implementations: one that is developed entirely in the Java programming language, and another developed in the C# language (for applications that will run within the Microsoft .NET Framework).

Perst for .NET supports standard and compact .NET frameworks and can thus be used to develop Microsoft Windows CE and Pocket PC applications.

Perst Lite is an implementation of Perst for Java for applications running on cell phones, personal digital assistants (PDAs) and other resource-constrained devices based on Sun MicrosystemsJava ME. Perst Lite is included in the Perst for Java distribution, and has a memory footprint approximately 30 percent smaller than standard Perst.

Contents

History

Perst was developed by Konstantin Knizhnik, a programmer living in Moscow, Russia, and released in 2003. In 2006, Knizhnik transferred distribution and commercial licensing of Perst to McObject, a for-profit company in Issaquah, Washington, United States. McObject develops and maintains the system, selling technical support and service contracts, as well as proprietary-licensed copies of Perst. Knizhnik is also still closely involved in developing Perst.

McObject develops another DBMS, eXtremeDB, which is an embedded database from an unrelated codebase.

Licensing

Users can redistribute and/or modify Perst under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or any later version. For individuals or organizations that cannot or do not wish to comply with the GPL, a commercial license for this software may be purchased from McObject.

Product features

Size

The Perst engine’s size is 5,000 lines of source code, and its run time random-access memory (RAM) needs range from 30K to 300K.[1]

Transactions

Perst transactions support the ACID properties (atomicity, consistency, isolation, durability) with automatic recovery.[2]

Querying

Perst provides a subset of SQL for filtering elements of a container class.[1] For access to persistent objects, Perst implements specialized collection classes including:

Schema evolution

To facilitate changes to an existing database design (database schema), Perst implements “lazy” database schema evolution. When an object instance is loaded from the database, its class descriptor is compared with the format of the class in the application. If they are not identical, and the object is to be changed, then the object is converted and stored in the new format.[3]

Additional features

Updates

July 2007

January 2008

February 2008

March 2008

June 2008

January 2009

February 2010

References

External links