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

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