DBMS > BigchainDB vs. LeanXcale vs. RocksDB vs. SAP Advantage Database Server vs. VoltDB

System Properties Comparison BigchainDB vs. LeanXcale vs. RocksDB vs. SAP Advantage Database Server vs. VoltDB

Editorial information provided by DB-Engines

Name

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 highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

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

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store

Key-value store
Relational DBMS

Key-value store

Relational DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	0.36
Rank	#280	Overall
	#40	Key-value stores
	#129	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.bigchaindb.com

www.leanxcale.com

rocksdb.org

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

www.voltdb.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

github.com/facebook/rocksdb/wiki

docs.voltdb.com

Developer

LeanXcale

Facebook, Inc.

Sybase, SAP

VoltDB Inc.

Initial release

2016

2015

2013

1993

2010

Current release

9.2.1, May 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

BSD

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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++

Java, C++

Server operating systems

Linux

Linux
Windows

Linux
OS X

for development

Data scheme

schema-free

yes

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

SQL

Support of SQL

yes

through Apache Derby

yes

only a subset of SQL 99

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

C++ API
Java API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
Java
Scala

C
C++
Go
Java
Perl
Python
Ruby

Delphi
Perl
PHP

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Sharding

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

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

Snapshots and command logging

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

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.