OrientDB is an Open Source NoSQL DBMS with the features of both Document and Graph DBMSs. It's written in Java and it's amazingly fast: it can store up to 150,000 records per second on common hardware. Even for a Document based database the relationships are managed as in Graph Databases with direct connections among records. You can traverse parts of or entire trees and graphs of records in a few milliseconds. Supports schema-less, schema-full and schema-mixed modes. Has a strong security profiling system based on user and roles and supports SQL amongst the query languages. Thanks to the SQL layer it's straightforward to use for people skilled in the Relational world.
Look also at Presentations with video and slides introducing OrientDB.
No. OrientDB adheres to the NoSQL movement even though it supports a subset of SQL as query language. In this way it's easy to start using it without having to learn too much new stuff. OrientDB is a Document Database but has the best features of other DBMSs. For example relationships are handled as in Graph Databases.
The most common reason applications scale out badly is, very often, the database. The database is the bottleneck of most applications. OrientDB scales out very well on a single machine. A single server does the work of about 125 servers running MySQL. The transactional engine can run in distributed systems supporting up to 302,231,454,903,657 billion (2^78) records for the maximum capacity of 19,807,040,628,566,084 Terabytes of data distributed on multiple disks in multiple nodes. Today only OrientDB Key/Value Server can run in a cluster with thousands of instances using a Distributed Hash Table algorithm. We're developing the distributed version of OrientDB as well.
OrientDB has been designed to be very fast. It inherits the best features and concepts from Object Databases, Graph DBMS and modern NoSQL engines. Furthermore it uses the own MVRB-Tree algorithm as a mix of Red-Black Tree and B+Tree. MVRB-Tree consumes about half memory of the Red-Black Tree implementation mantaining the original speed while it balances the tree on insertion/update. Furthermore the MVRB-Tree allows fast retrieving and storing of nodes in persistent way.
It all began on 2009 when Luca Garulli was searching for super fast and flexible storage for an ambitious project. After having tried different RDBMSs he worked on the available NoSQL products. Not one had all the features he needed. So in a weekend he got the challenge to see if the "old" low-level storage algorithms of Orient ODBMS, an Object Database Luca created in 1999 written in C++, could be reused in Java to develop a brand new graph-document DBMS. It worked! And this is the reason OrientDB exists today.
Orient ODBMS was the very first version of the Orient engine developed in C++ in 1998. Today OrientDB has been totally rewritten in Java in the form of a Document database but with the previous main goal: performance. However, now you can find the [Object Database], but it's a wrapper built on top of the Document Database. It maps transparently OrientDB document records to POJOs.
Take a look at GraphDB comparison and DocumentDB comparison.
Yes. OrientDB is totally written in Java and can run on any platform without configuration and installation. The full Server distribution is about 1Mb without the demo database. Do you develop with a language different than Java? No problem, look at the [Programming Language Bindings].
OrientDB is free for any use (Apache 2 license). If you are in production don't miss the professional support service. For courses and training look at the on-line course catalog.
| OrientDB is available on the cloud through NuvolaBase.com. FREE accounts are available for small sized databases. |
Start to learn about OrientDB from the WiKi Main page. For any questions visit the OrientDB Community Group. Need help? Go to the Online support. Do you want to hear about OrientDB in a conference? Take a look at the Events page.
