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

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

Editorial information provided by DB-Engines

Name

Description

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

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

Primary database model

Document store
Object oriented DBMS

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

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

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

Score	16.59
Rank	#36	Overall
	#5	Document 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

Website

github.com/boltdb/bolt

www.couchbase.com

www.firebolt.io

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

origodb.com

Technical documentation

docs.couchbase.com

docs.firebolt.io

origodb.com/docs

Developer

Couchbase, Inc.

Firebolt Analytics Inc.

Rocket Software, originally Martin Phillips

Robert Friberg et al

Initial release

2013

2011

2020

1993

2009

under the name LiveDB

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

3.4-12

License

Commercial or Open Source

Open Source

MIT License

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

Open Source

GPLv2, extended commercial license available

Open Source

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, C++, Go and Erlang

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
Windows

Data scheme

schema-free

yes

with some exceptions

yes

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

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

APIs and other access methods

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

.Net
ODBC
RESTful HTTP API

.NET Client API
HTTP API
LINQ

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Go
JavaScript (Node.js)
Python

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes

Triggers

yes

via the TAP protocol

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

Automatic Sharding

yes

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

including cross data center replication
Source-replica replication

depending on storage layer

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

In-memory capabilities

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

yes

Ephemeral buckets

yes

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base 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.