SQLAlchemy

Voldemort is not a relational database, it does not attempt to satisfy arbitrary relations while satisfying ACID properties. Nor is it an object database that attempts to transparently map object reference graphs. Nor does it introduce a new abstraction such as document-orientation. It is basically just a big, distributed, persistent, fault-tolerant hash table. For applications that can use an O/R mapper like active-record or hibernate this will provide horizontal scalability and much higher availability but at great loss of convenience. For large applications under internet-type scalability pressure, a system may likely consist of a number of functionally partitioned services or APIs, which may manage storage resources across multiple data centers using storage systems which may themselves be horizontally partitioned. For applications in this space, arbitrary in-database joins are already impossible since all the data is not available in any single database.

Perst is McObject’s open source, dual license, object-oriented embedded database system (ODBMS). It is available in one edition developed as an all-Java embedded database, and another implemented in C# (for Microsoft .NET Framework applications). Perst gives developers the ability to store, sort, and retrieve objects in their applications with maximum speed and with low memory and storage overhead while leveraging the object-oriented paradigm of Java and C#. In the TestIndex and PolePosition benchmarks, Perst displays one of its strongest features: its significant performance advantage over Java and .NET embedded database alternatives. Perst stores data directly in Java and .NET objects, eliminating the translation required for storage in relational and object-relational databases. This boosts run-time performance. Perst’s core consists of only five thousand lines of code. The small footprint imposes minimal demands on system resources.