* Single Instance - You can use ArangoDB as a specialized database for key/values, documents or graphs and even mix up those data models in one query. * Cluster - Synchronous replication. Automatic failover. Self-organizing cluster state management. Fast cluster startup. Easy maintenance. Multiple data models. All with an ArangoDB Cluster. * Mixed Services - Modern Architectures demand scalability, polyglot persistence and low maintenance. Modern data center operating systems put your data cluster on autopilot. * Graph - ArangoDB provides also the full feature set of a mature graph store (e.g. pattern matching, shortest path, full blown traversals) and due to a little magic it can perform graph queries very fast compared to many other leading graph solutions. * Document - You can store as many attributes in a document as you like (default size of a document is 32MB, but configurable to your needs). ArangoDB has a wide feature-set for querying and working with documents like joins, secondary indexes or acid transactions. You can horizontally scale join usage to the technically possible.

* In-process. BergDB is designed for application databases and runs in the same process as the application code for highest possible performance and for reduced complexity. * Widely cross-platform. The database library is available to any JVM or .NET language. * Scalable. BergDB is suitable for applications storing small amounts of data, say 1 kB. Yet, it scales to store terabytes of data in billions of entries. * Time-key-value data model. Data is stored as time-key-value entries. * Schemaless. Values stored in the database are raw byte arrays, Unicode strings, or objects (could also be called "documents"). * Secondary indexes. Besides the primary index, BergDB supports secondary indexing of objects based on object field values. * Code only. The developer use ordinary Java (or any other .NET/JVM language) code to store and retrieve data. * Simple API. The database runs embedded in your application process for highest possible performance. * Transaction throughput. BergDB is designed to be fast for both traditional rotating disk drives and for solid state drives. * Always consistent. Changes to the database state is always made using atomic transactions with the highest isolation level: serializable.