DBMS > BoltDB vs. Firebolt vs. OpenQM vs. OrigoDB vs. RocksDB

System Properties Comparison BoltDB vs. Firebolt vs. OpenQM vs. OrigoDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Highly scalable cloud data warehouse and analytics product

Forked from Clickhouse

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

A fully ACID in-memory object graph database

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

Primary database model

Key-value store

Relational DBMS

Multivalue DBMS

Document store
Object oriented DBMS

Key-value store

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	1.73
Rank	#140	Overall
	#63	Relational DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

github.com/boltdb/bolt

www.firebolt.io

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

origodb.com

rocksdb.org

Technical documentation

docs.firebolt.io

origodb.com/docs

github.com/facebook/rocksdb/wiki

Developer

Firebolt Analytics Inc.

Rocket Software, originally Martin Phillips

Robert Friberg et al

Facebook, Inc.

Initial release

2013

2020

1993

2009

under the name LiveDB

2013

Current release

3.4-12

9.2.1, May 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

GPLv2, extended commercial license available

Open Source

BSD

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
Windows

Linux

Data scheme

schema-free

yes

with some exceptions

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

.Net
ODBC
RESTful HTTP API

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

Go
JavaScript (Node.js)
Python

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

yes

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

yes

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

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.