DBMS > BigchainDB vs. KairosDB vs. Linter vs. SQLite vs. Transbase

System Properties Comparison BigchainDB vs. KairosDB vs. Linter vs. SQLite vs. Transbase

Editorial information provided by DB-Engines

Name

Description

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

Distributed Time Series DBMS based on Cassandra or H2

RDBMS for high security requirements

Widely used embeddable, in-process RDBMS

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store

Time Series DBMS

Relational DBMS

Secondary database models

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.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.bigchaindb.com

github.com/kairosdb/kairosdb

linter.ru

www.sqlite.org

www.transaction.de/en/products/transbase.html

Technical documentation

bigchaindb.readthedocs.io/en/latest

kairosdb.github.io

www.sqlite.org/docs.html

www.transaction.de/en/products/transbase/features.html

Developer

relex.ru

Dwayne Richard Hipp

Transaction Software GmbH

Initial release

2016

2013

1990

2000

1987

Current release

1.2.2, November 2018

3.45.3 (15 April 2024), April 2024

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache 2.0

commercial

Open Source

Public Domain

commercial

free development license

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

Java

C and C++

Server operating systems

Linux

Linux
OS X
Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

server-less

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

yes

APIs and other access methods

CLI Client
RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

Java
JavaScript

Node.js
PHP
Python

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

User concepts

Access control

yes

simple password-based access control

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.