DBMS > BigchainDB vs. MySQL vs. TimesTen vs. Warp 10

System Properties Comparison BigchainDB vs. MySQL vs. TimesTen vs. Warp 10

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

Widely used open source RDBMS

In-Memory RDBMS compatible to Oracle

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

www.bigchaindb.com

www.mysql.com

www.oracle.com/database/technologies/related/timesten.html

www.warp10.io

Technical documentation

bigchaindb.readthedocs.io/en/latest

dev.mysql.com/doc

docs.oracle.com/database/timesten-18.1

www.warp10.io/content/02_Getting_started

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

SenX

Initial release

2016

1995

1998

2015

Current release

8.4.0, April 2024

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

Apache License 2.0

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Python

C and C++

Java

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

CLI Client
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP API
Jupyter
WebSocket

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

proprietary syntax

PL/SQL

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

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

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

by means of logfiles and checkpoints

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

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.