DBMS > BigchainDB vs. HEAVY.AI vs. jBASE vs. Kinetica vs. SQLite

System Properties Comparison BigchainDB vs. HEAVY.AI vs. jBASE vs. Kinetica vs. SQLite

Editorial information provided by DB-Engines

Name

Description

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

A robust multi-value DBMS comprising development tools and middleware

Fully vectorized database across both GPUs and CPUs

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Spatial DBMS

Spatial DBMS
Time Series DBMS

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	1.43
Rank	#160	Overall
	#3	Multivalue DBMS

Score	0.69
Rank	#234	Overall
	#107	Relational DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

www.bigchaindb.com

github.com/heavyai/heavydb
www.heavy.ai

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.kinetica.com

www.sqlite.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.heavy.ai

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

docs.kinetica.com

www.sqlite.org/docs.html

Developer

HEAVY.AI, Inc.

Rocket Software (formerly Zumasys)

Kinetica

Dwayne Richard Hipp

Initial release

2016

1991

2012

2000

Current release

5.10, January 2022

5.7

7.1, August 2021

3.45.2 (12 March 2024), March 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache Version 2; enterprise edition available

commercial

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

C, C++

Server operating systems

Linux

AIX
Linux
Windows

Linux

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

optional

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

Embedded SQL for jBASE in BASIC

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

JDBC
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

.Net
Basic
Jabbascript
Java

C++
Java
JavaScript (Node.js)
Python

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

yes

user defined functions

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

Round robin

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

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

User concepts

Access control

yes

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

Access rights for users and roles on table level

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.