* No need of service installation and communication protocol. The fastest way to use it. You have direct access to the Database memory and you can manipulate objects and data in a very fast way. * Installed as Windows Service, it can be used as a network document store. You can use rest service or wcf service to access it. It's not different from the previous way to use it but you have a networking protocol and so it's not fast as the previous one. * Built using Command Query Responsibility Segregation pattern in mind. * Store data as Bson-like Documents. * Accessible via Rest * Accessible via WCF * Peer to peer synchronization and event propagation enabled. * Pluggable via Server Plugin. * Use Linq syntax for queries.

* Built for Speed - OrientDB was engineered from the ground up with performance as a key specification. It is fast on both read and write operations. On writes, it can store up to 120,000 records per second*. * No More Joins - OrientDB can embed documents like any other document database, but also supports relationships. It doesn’t use the costly JOIN. Instead, OrientDB uses super-fast, persistent pointers between records, taken from the graph database world. You can traverse parts of or entire trees and graphs of records in just a few milliseconds. * Unmatched Flexibility - Replacing your DBMS, once it no longer meets requirements, can be a huge cost in time and resources. * Zero-Configuration Multi-Master Architecture - OrientDB supports a Multi-Master + Sharded architecture, so all the servers are masters. This provides horizontal scalability and reliability. * Elastic Linear Scalability - With a master-slave architecture, the master often becomes the bottleneck. With OrientDB, throughput is not limited by a single server. * Easy to Install and Use - OrientDB is written entirely in Java and can run on any platform without configuration and installation. It’s a drop in replacement for the most common existing graph databases in deployment today.