DBMS > BigchainDB vs. Kinetica vs. Microsoft SQL Server vs. Percona Server for MongoDB vs. VoltDB

System Properties Comparison BigchainDB vs. Kinetica vs. Microsoft SQL Server vs. Percona Server for MongoDB vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

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

Fully vectorized database across both GPUs and CPUs

Microsofts flagship relational DBMS

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

www.bigchaindb.com

www.kinetica.com

www.microsoft.com/en-us/sql-server

www.percona.com/mongodb/software/percona-server-for-mongodb

www.voltdb.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.kinetica.com

learn.microsoft.com/en-US/sql/sql-server

docs.percona.com/percona-distribution-for-mongodb

docs.voltdb.com

Developer

Kinetica

Microsoft

Percona

VoltDB Inc.

Initial release

2016

2012

1989

2015

2010

Current release

7.1, August 2021

SQL Server 2022, November 2022

3.4.10-2.10, November 2017

11.3, April 2022

License

Commercial or Open Source

Open Source

AGPL v3

commercial

restricted free version is available

Open Source

GPL Version 2

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

C++

Java, C++

Server operating systems

Linux

Linux
Windows

Linux

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

only a subset of SQL 99

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

proprietary protocol using JSON

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

JavaScript

Java

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

yes, but depending on the SQL-Server Edition

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

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

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

GPU vRAM or System RAM

yes

via In-Memory Engine

User concepts

Access control

yes

Access rights for users and roles on table level

fine grained access rights according to SQL-standard

Access rights for users and roles

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.