DBMS > BoltDB vs. Couchbase vs. HarperDB vs. Riak KV

System Properties Comparison BoltDB vs. Couchbase vs. HarperDB vs. Riak KV

Please select another system to include it in the comparison.

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

HarperDB takes the "stack" out of "tech stack" by combining an ultra-fast document-style data store, in-memory cache, real-time message broker, and your application components into a single distributed technology.

Distributed, fault tolerant key-value store

Primary database model

Key-value store

Document store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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.70
Rank	#225	Overall
	#31	Key-value stores

Score	16.74
Rank	#33	Overall
	#5	Document stores

Score	0.55
Rank	#243	Overall
	#38	Document stores

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Website

github.com/boltdb/bolt

www.couchbase.com

www.harperdb.io

Technical documentation

docs.couchbase.com

docs.harperdb.io/docs

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Couchbase, Inc.

HarperDB

OpenSource, formerly Basho Technologies

Initial release

2013

2011

2017

2009

Current release

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

3.1, August 2021

3.2.0, December 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

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

commercial

free community edition available

Open Source

Apache version 2, commercial enterprise edition

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

Node.js

Erlang

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Linux
OS X

Data scheme

schema-free

dynamic schema

schema-free

Typing

predefined data types such as float or date

yes

JSON data types

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.

Secondary indexes

yes

restricted

SQL

Support of SQL

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

SQL-like data manipulation statements

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

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

HTTP API
Native Erlang Interface

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

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

Custom Functions

since release 3.1

Erlang

Triggers

yes

via the TAP protocol

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Automatic Sharding

A table resides as a whole on one (or more) nodes in a cluster

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

including cross data center replication
Source-replica replication

yes

the nodes on which a table resides can be defined

selectable replication factor

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

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

yes

ACID

Atomic execution of specific operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

yes

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 for users and roles

yes, using Riak Security

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.