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

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