DBMS > BigchainDB vs. IBM Db2 vs. Snowflake vs. Tarantool

System Properties Comparison BigchainDB vs. IBM Db2 vs. Snowflake vs. Tarantool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Common in IBM host environments, 2 different versions for host and Windows/Linux

Cloud-based data warehousing service for structured and semi-structured data

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

www.bigchaindb.com

www.ibm.com/products/db2

www.snowflake.com

www.tarantool.io

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.ibm.com/docs/en/db2

docs.snowflake.net/manuals/index.html

www.tarantool.io/en/doc

Developer

IBM

Snowflake Computing Inc.

Initial release

2016

1983

host version

2014

2008

Current release

12.1, October 2016

2.10.0, May 2022

License

Commercial or Open Source

Open Source

AGPL v3

commercial

free version is available

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Python

C and C++

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows
z/OS

hosted

BSD
Linux
macOS

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Full-featured ANSI SQL support

APIs and other access methods

CLI Client
RESTful HTTP API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

CLI Client
JDBC
ODBC

Open binary protocol

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

user defined functions

Lua, C and SQL stored procedures

Triggers

yes

similar concept for controling cloud resources

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

yes

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

with separate tools (MQ, InfoSphere)

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, full featured in-memory storage engine with persistence

User concepts

Access control

yes

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.