DBMS > BigchainDB vs. IRONdb vs. Kinetica vs. SAP HANA vs. Yaacomo

System Properties Comparison BigchainDB vs. IRONdb vs. Kinetica vs. SAP HANA vs. Yaacomo

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Fully vectorized database across both GPUs and CPUs

In-memory, column based data store. Available as appliance or cloud service

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial 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	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.bigchaindb.com

www.circonus.com/solutions/time-series-database/

www.kinetica.com

www.sap.com/products/hana.html

yaacomo.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.circonus.com/irondb/category/getting-started

docs.kinetica.com

help.sap.com/hana

Developer

Circonus LLC.

Kinetica

SAP

Q2WEB GmbH

Initial release

2016

2017

2012

2010

2009

Current release

V0.10.20, January 2018

7.1, August 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Python

C and C++

C, C++

Server operating systems

Linux

Appliance or cloud-service

Android
Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like DML and DDL statements

yes

APIs and other access methods

CLI Client
RESTful HTTP API

HTTP API

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes, in Lua

user defined functions

SQLScript, R

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

Automatic, metric affinity per node

Sharding

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

configurable replication factor, datacenter aware

Source-replica replication

yes

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 per node, eventual consistency across nodes

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

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

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

yes

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.