DBMS > BigchainDB vs. Kinetica vs. SQLite vs. Sqrrl vs. ToroDB

System Properties Comparison BigchainDB vs. Kinetica vs. SQLite vs. Sqrrl vs. ToroDB

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

ToroDB 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

Fully vectorized database across both GPUs and CPUs

Widely used embeddable, in-process RDBMS

Adaptable, secure NoSQL built on Apache Accumulo

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.bigchaindb.com

www.kinetica.com

www.sqlite.org

sqrrl.com

github.com/torodb/server

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.kinetica.com

www.sqlite.org/docs.html

Developer

Kinetica

Dwayne Richard Hipp

Amazon

originally Sqrrl Data, Inc.

8Kdata

Initial release

2016

2012

2000

2012

2016

Current release

7.1, August 2021

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

Public Domain

commercial

Open Source

AGPL-V3

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

Server operating systems

Linux

server-less

Linux

All OS with a Java 7 VM

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes

string, integer, double, boolean, date, object_id

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

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
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

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

none

Sharding

making use of Hadoop

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

none

selectable replication factor

making use of Hadoop

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

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

GPU vRAM or System RAM

yes

User concepts

Access control

yes

Access rights for users and roles on table level

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

Access rights for users and roles

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.