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

* EJDB is good for: - In-process database for standalone desktop applications. (The SQLite niche); - Games development; - Simple server-side solution; - Whenever a fast in-process data-communication with storage layer is much preferred over TCP/IP transport; * Generic key-value storage using Hash or B+ tree index. * Collection level transactions. * Mongodb-like queries and overall philosophy. * Collection joins in query language.