The easiest way to make your Python application Persistent. Used in ZODB, NEO, ZeroDB and Durus. PermaLink
Alternatives to Persistent Python
A brief examination of the alternatives to Peristent Python
Durus Database (14)
Durus is a light-weight clone of ZODB.
NEO supports Persistent Python on a cluster of servers.
ZeroDB Database (22)
zerodb is an encrypted database where the server does not have access to the data.
ZODB: An OODB For Python (67)
ZODB is an object-oriented database for Python developers. You can persist arbitrary Python structures. It is particularly good for trees and graphs.
- Alternatives to Persistent Python (1)
- Persistent Python (107)
- Database Libraries (146)
- Python Libraries (630)
- Python Software (1041)
The easiest way to make your python application persistent is to subclass off of Persistent (Object), PersistentList, PersistentDict and PersistentSet provided by the persistent library. With Persistent Python, you no longer have to think about reading and writing objects. Just write your business logic, and Persistent Python will load and save your objects when required. If an object is reachable it is persistent.
You can run Persistent Python on whichever database is best for your application. ZODB is the market leader for Persistent Python. ZeroDb is the hot new startup, the server knows nothing, all data is encrypted and decrypted on the client. Indeed Jim Fulton, the author of ZODB, now works for ZeroDB. Neo is great for large data sets, it runs on a cluster. Durus is very light weight and high persormance, but seems quite inactive.
With servers moving from hard drives to SSD drives, you now can get great performance from an object database based on persistent python.