DBMS > BigchainDB vs. FatDB vs. Riak KV vs. RocksDB vs. SAP Advantage Database Server

System Properties Comparison BigchainDB vs. FatDB vs. Riak KV vs. RocksDB vs. SAP Advantage Database Server

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.

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

Distributed, fault tolerant key-value store

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

Low-cost RDBMS with access to ISAM and FoxPro data structures

Primary database model

Document store

Document store
Key-value store

Key-value store

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

Key-value store

Relational DBMS

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

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

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

www.bigchaindb.com

rocksdb.org

www.sap.com/products/advantage-database-server.html

Technical documentation

bigchaindb.readthedocs.io/en/latest

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

github.com/facebook/rocksdb/wiki

Developer

FatCloud

OpenSource, formerly Basho Technologies

Facebook, Inc.

Sybase, SAP

Initial release

2016

2012

2009

2013

1993

Current release

3.2.0, December 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

BSD

commercial

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

Erlang

C++

Server operating systems

Linux

Windows

Linux
OS X

Linux

Linux
Windows

Data scheme

schema-free

yes

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

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

APIs and other access methods

CLI Client
RESTful HTTP API

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

HTTP API
Native Erlang Interface

C++ API
Java API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

Go
Haskell
Java
JavaScript
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

C
C++
Go
Java
Perl
Python
Ruby

Delphi
Perl
PHP

Server-side scripts

Stored procedures

yes

via applications

Erlang

yes

Triggers

yes

via applications

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

yes

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,with MongoDB ord RethinkDB

yes

In-memory capabilities

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

yes

caching of (temporary) tables can be configured

User concepts

Access control

yes

Can implement custom security layer via applications

yes, using Riak Security

fine grained access rights according to SQL-standard

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.