DBMS > BigchainDB vs. Cubrid vs. HarperDB vs. Riak KV vs. SQLite

System Properties Comparison BigchainDB vs. Cubrid vs. HarperDB vs. Riak KV vs. SQLite

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Distributed, fault tolerant key-value store

Widely used embeddable, in-process RDBMS

Primary database model

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

Relational DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.bigchaindb.com

cubrid.com (korean)
cubrid.org (english)

www.harperdb.io

www.sqlite.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

cubrid.org/manuals

docs.harperdb.io/docs

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

www.sqlite.org/docs.html

Developer

CUBRID Corporation, CUBRID Foundation

HarperDB

OpenSource, formerly Basho Technologies

Dwayne Richard Hipp

Initial release

2016

2008

2017

2009

2000

Current release

11.0, January 2021

3.1, August 2021

3.2.0, December 2022

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache Version 2.0

commercial

free community edition available

Open Source

Apache version 2, commercial enterprise edition

Open Source

Public Domain

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

Python

C, C++, Java

Node.js

Erlang

Server operating systems

Linux

Linux
Windows

Linux
OS X

server-less

Data scheme

schema-free

yes

dynamic schema

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

JSON data types

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL

Support of SQL

yes

SQL-like data manipulation statements

yes

SQL-92 is not fully supported

APIs and other access methods

CLI Client
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

HTTP API
Native Erlang Interface

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

.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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

Custom Functions

since release 3.1

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

yes

the nodes on which a table resides can be defined

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

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

User concepts

Access control

yes

fine grained access rights according to SQL-standard

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.