* CRUD * KeyValue and KeyOnly tables * Unique and non-unique indexes * Unique and non-unique composite indexes * SQL like query language * Transactions support * Concurrency control, thread safe * Memory management * Scalable hot MasterSlave and MasterMaster replications * On disk and in memory databases supported * Automatically create databases * Zero configuration, copy and run, purely managed code * Dynamic columns * Different types with different indexes can be stored in same table * Persistence + ORM + Cache + Embeddable, ONE STOP solution * ResultSet compatible with LINQ * High performance, no dependencies * Update Increment * Selecting Tracer

* 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.