DBMS > Altibase vs. Apache Druid vs. BigchainDB vs. MySQL

System Properties Comparison Altibase vs. Apache Druid vs. BigchainDB vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An enterprise grade, high-performance RDBMS

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Widely used open source RDBMS

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	1.00
Rank	#194	Overall
	#91	Relational DBMS

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

druid.apache.org/docs/latest/design

bigchaindb.readthedocs.io/en/latest

dev.mysql.com/doc

Developer

Altibase

Apache Software Foundation and contributors

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

1999

2012

2016

1995

Current release

v7.3, 2023, August 2023

29.0.1, April 2024

8.3.0, January 2024

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

Open Source

Apache license v2

Open Source

AGPL v3

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

C++

Java

Python

C and C++

Server operating systems

AIX
HP-UX
Linux

Linux
OS X
Unix

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-less columns are supported

schema-free

yes

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

ANSI SQL-92

SQL for querying

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
Proprietary protocol

JDBC
RESTful HTTP/JSON API

CLI Client
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C++
Java

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

Server-side scripts

Stored procedures

stored procedures and stored functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

selectable replication factor

Multi-source replication
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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

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

fine grained access rights according to SQL-standard

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

yes

Users with fine-grained authorization concept

no user groups or 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.