Misplaced Pages

Prevayler

Article snapshot taken from[REDACTED] with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
In-RAM database
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Prevayler" – news · newspapers · books · scholar · JSTOR (March 2014) (Learn how and when to remove this message)
The topic of this article may not meet Misplaced Pages's general notability guideline. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted.
Find sources: "Prevayler" – news · newspapers · books · scholar · JSTOR (March 2014) (Learn how and when to remove this message)

Prevayler is an open-source (BSD) system-prevalence layer for Java: it transparently persists plain old Java objects. It is an in-RAM database backed by snapshots of the system via object serialization, which are loaded after a system crash to restore state. Changes to data happen via transaction operations on objects made from serializable classes. Prevayler's development was started by Klaus Wuestefeld.

Read operations are three to four orders of magnitude faster with Prevayler when compared to traditional database systems since all objects are always in RAM and in-process.

Prevayler requires enough RAM to keep the entire system state.

References

  1. Sam-Bodden & Judd 2008, p. 330.

Works cited

See also

External links

Stub icon

This database software-related article is a stub. You can help Misplaced Pages by expanding it.

Categories:
Prevayler Add topic