DBMS > OpenQM vs. RocksDB

System Properties Comparison OpenQM vs. RocksDB

Please select another system to include it in the comparison.

Our visitors often compare OpenQM and RocksDB with InfluxDB, Elasticsearch and TimescaleDB.

Editorial information provided by DB-Engines

Name

Description

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

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

Primary database model

Multivalue DBMS

Key-value store

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

Score	0.58
Rank	#262	Overall
	#10	Multivalue DBMS

Score	4.57
Rank	#87	Overall
	#13	Key-value stores

Website

www.openqm.com

rocksdb.org

Technical documentation

www.openqm.com/support/documentation

github.com/facebook/rocksdb/wiki

Developer

Martin Phillips

Facebook, Inc.

Initial release

1993

2013

Current release

3.4-12

7.10.2, March 2023

License

Commercial or Open Source

Open Source

GPLv2, extended commercial license available

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++

Server operating systems

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux

Data scheme

yes

with some exceptions

schema-free

Typing

predefined data types such as float or date

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

Secondary indexes

yes

SQL

Support of SQL

APIs and other access methods

C++ API
Java API

Supported programming languages

.Net
Basic
C
Java
Objective C
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

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

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.