DBMS > BigchainDB vs. Cubrid vs. FatDB vs. Riak KV

System Properties Comparison BigchainDB vs. Cubrid vs. FatDB vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Distributed, fault tolerant key-value store

Primary database model

Document store

Relational DBMS

Document store
Key-value store

Key-value store

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

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	1.31
Rank	#169	Overall
	#78	Relational DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

www.bigchaindb.com

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

Technical documentation

bigchaindb.readthedocs.io/en/latest

cubrid.org/manuals

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

Developer

CUBRID Corporation, CUBRID Foundation

FatCloud

OpenSource, formerly Basho Technologies

Initial release

2016

2008

2012

2009

Current release

11.0, January 2021

3.2.0, December 2022

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache Version 2.0

commercial

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

Python

C, C++, Java

Erlang

Server operating systems

Linux

Linux
Windows

Windows

Linux
OS X

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

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

yes

Via inetgration in SQL Server

APIs and other access methods

CLI Client
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

HTTP API
Native Erlang Interface

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

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

Java Stored Procedures

yes

via applications

Erlang

Triggers

yes

via applications

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

selectable replication factor

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
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

In-memory capabilities

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

User concepts

Access control

yes

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

An Introduction to BigchainDB, a Popular Blockchain Database
17 September 2020, Open Source For You

Blockchain Database Startup BigchainDB Raises €3 Million
27 September 2016, CoinDesk

What is BigchainDB Technology & How it works and the Characteristics?
26 August 2017, Blockchain Council

Using BigchainDB: A Database with Blockchain Characteristics
20 January 2022, Open Source For You

Capgemini and Ascribe Build Blockchain Project for Banking Loyalty Rewards
7 June 2016, Bitcoin Magazine

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page