DBMS > OpenQM vs. Oracle Berkeley DB vs. OrientDB vs. RocksDB

System Properties Comparison OpenQM vs. Oracle Berkeley DB vs. OrientDB vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

QpenQM is a high-performance, self-tuning, multi-value DBMS

Widely used in-process key-value store

Multi-model DBMS (Document, Graph, Key/Value)

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Multivalue DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store
Graph DBMS
Key-value store

Key-value store

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.oracle.com/database/technologies/related/berkeleydb.html

orientdb.org

rocksdb.org

Technical documentation

docs.oracle.com/cd/E17076_05/html/index.html

www.orientdb.com/docs/last/index.html

github.com/facebook/rocksdb/wiki

Developer

Rocket Software, originally Martin Phillips

Oracle

originally developed by Sleepycat, which was acquired by Oracle

OrientDB LTD; CallidusCloud; SAP

Facebook, Inc.

Initial release

1993

1994

2010

2013

Current release

3.4-12

18.1.40, May 2020

3.2.29, March 2024

8.11.4, April 2024

License

Commercial or Open Source

Open Source

GPLv2, extended commercial license available

Open Source

commercial license available

Open Source

Apache version 2

Open Source

BSD

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, Java, C++ (depending on the Berkeley DB edition)

Java

C++

Server operating systems

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

All OS with a Java JDK (>= JDK 6)

Linux

Data scheme

yes

with some exceptions

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

schema-free

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

SQL-like query language, no joins

APIs and other access methods

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

C++ API
Java API

Supported programming languages

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Java, Javascript

Triggers

yes

only for the SQL API

Hooks

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights can be defined down to the item level

Access rights for users and roles; record level security configurable

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.