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

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