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 Database that support hybrid Document Database features London, UK – Orient Technologies (http://www.orientechnologies.com/) and Hazelcast (http://www.hazelcast.com) today announced that OrientDB has gained a multi-master replication feature powered by Hazelcast. Clustering multiple server nodes is the most significant feature of OrientDB 1.6. Databases can be replicated across heterogeneous server nodes in multi-master mode achieving the best of scalability and performance. “I think one of the added value of OrientDB against all the NoSQL products is the usage of Hazelcast while most of the others use Yahoo ZooKeeper to manage the cluster (discovery, split brain network, etc) and something else for the transport layer.” said Luca Garulli, CEO of Orient Technologies. “With ZooKeeper configuration is a nightmare, while Hazelcast let you to add OrientDB servers with ZERO configuration. This has been a big advantage for our clients and everything is much more ‘elastic’, specially when deployed on the Cloud. We’ve used Hazelcast not only for the auto-discovery, but also for the transport layer. Thanks to this new architecture all our clients can scale up horizontally by adding new servers without stopping or reconfigure the cluster”. “We are amazed by the speed with which OrientDB has adopted Hazelcast and we are delighted to see such excellent technologists teaming up with Hazelcast.” said Talip Ozturk, CEO of Hazelcast. “We work hard to make the best open source in-memory data grid on the market and are happy to see it being used in this way.” Both Hazelcast and Orient Technologies are providing professional open source support to their respective projects under the Apache software license. Full article: http://orientechnologies.blogspot.it/2013/11/orientdb-becomes-distributed-using.html
Release Notes: This hotfix fixed database corruption on shutdown.
Release Notes: Hotfixes.
Release Notes: This release features a new cluster strategy for picking the cluster, support for SSL on binary and HTTP protocols, and new “script”, “next”, “prev”, "move”, and “eval” console commands. Distributed now supports sharding and simplified (JSON) configuration. Graph has new functions to return the traversed items. For SQL, a new PARALLEL keyword runs the query on multiple threads. “INSERT INTO … SELECT” was added for copying records. Full-text and Geospatial Lucene indexes were provided (as a plugin), WAL (Journal) support was added for Hash-Index so that it can be used in transactions. Studio now has bookmarks for queries.
Release Notes: For Core, this release supports retro-compatibility for databases created with OrientDB v1.5 or higher, improves performance on ORDER BY against indexes, and improves performance on RENAME CLASS. For Graph, it adds support for vertex-centric traversal by using SQL. For SQL, it adds an UPSERT keyword to execute an INSERT or UPDATE based on a condition, and UPDATE can now ADD to sub-document fields. For Indexes, it adds support for external engines. For Studio, it adds a new Query Timeline to the History and a new Index Panel.
Release Notes: A new LINKBag to manage LINKS. This drastically improves performance. SQL: a new LOCK keyword to specify a locking strategy; a new RETURNING keyword to allow UPDATE and DELETE commands to return modified records; include() and exclude() to respectively include or exclude fields of documents; and support for LET in the UPDATE and DELETE commands. Graph API: support for an ordered edge list; new detach() and attach() methods to work with Graph elements offline; and new OrientGraphFactory to manage pooled instances. HTTP: support for headers and partial updates. Database deployment is now chunked.