OrientDB is an Open Source NoSQL DBMS with the features of both Document and Graph DBMSs. Written in Java, it is incredibly 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 those skilled in the relational database world.
OrientDB can embed documents like any other Document Database, but can also connect documents like a Relational Database. The main difference is that OrientDB doesn’t use the costly JOIN, but rather uses direct, super-fast links taken from the Graph Database world. No duplicates: the resulting database is smaller and lighter Faster: a smaller database means better usage of RAM thus allowing more caching Upon loading the order document, OrientDB will assemble the entire document by fetching all the connections transparently.
OrientDB has been designed to be very fast. It inherits the best features and concepts from Document, Graph and Object Databases. 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 maintaining 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.
The most common reason applications scale up badly is, very often, the database. The database is the bottleneck of most applications. OrientDB scales up 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.
When you need more throughput, simply add a new server in the network and it will join the current distributed server cluster. Synchronization occurs automatically as soon as the server is brought online. You can’t get it much easier than that!
What happens when a server node crashes? The server cluster redistributes the load across the available nodes and all the clients connected to the node in failure are automatically switched to an available server node with no fail-over to the application level.
OrientDB is a Document-Graph DBMS, so you can compare it against DocumentDB and GraphDB products. If you already know MongoDB, look at OrientDB vs MongoDB page. Also, take a look at GraphDB comparison and DocumentDB comparison. What about speed? Download the independent Benchmark between GraphDB products “XGDBench: A Benchmarking Platform for Graph Stores in Exascale Clouds“ by Tokyo Institute of Technology and IBM Research.
Absolutely. OrientDB is written completely 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.