OrientDB is a NoSQL DBMS which can store 150,000 documents per second on common hardware. Even with a document-based database, the relationships are managed as in graph databases, with direct connections among records. You can traverse entire or parts of trees and graphs of records in a few milliseconds. It supports schema-less, schema-full, and schema-mixed modes, has a strong security profiling system based on users and roles, and supports SQL between the query languages. Thanks to the SQL layer, it's straightforward to use for people skilled in the relational world.
|Tags||NoSQL Database Document Repositories graph database|
|Operating Systems||Cross Platform|
OrientDB becomes Distributed using Hazelcast, Leading Open Source In-Memory Data Grid
Elastic Distributed scalability added to OrientDB, a Graph...
Release Notes: This release adds a COLLATE keyword for case-insensitive comparison and fixes 22 issues.
Release Notes: This release fixes bugs.
Release Notes: SBTree: a new index engine with support for transactions and range queries. Distributed: a new architecture based on Hazelcast, new Distributed Transaction support across nodes, and a new Database Sharding feature. Studio: a total rewrite in a new tool hosted on separate project. HTTP: execute commands in batch mode, partial document updates, JSON as a return of creating and updating documents, and management of multiple databases in the same connection. Plugins: a new hot deployment plugin.
Release Notes: This release adds bugfixes.
Release Notes: There is a new PLOCAL (Paginated Local) storage engine. In comparison with LOCAL, it's more durable (no usage of MMAP) and supports better concurrency on parallel transactions. There is a new Hash Index type with better performance on lookups (does not support ranges). There is a new "transactional" SQL command to execute commands inside a tx. Import now migrates RIDs, allowing it to import databases in a different one from the original. A "breadth first" strategy has been added on traversing. The server can limit maximum live connections (to prevent DOS). Fetch plan support in SQL statements and in binary protocol.