DBMS > BigchainDB vs. Citus vs. Google Cloud Datastore vs. Heroic vs. MySQL

System Properties Comparison BigchainDB vs. Citus vs. Google Cloud Datastore vs. Heroic vs. MySQL

Editorial information provided by DB-Engines

Name

Description

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

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Document store

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	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

www.bigchaindb.com

www.citusdata.com

cloud.google.com/datastore

github.com/spotify/heroic

www.mysql.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.citusdata.com

cloud.google.com/datastore/docs

spotify.github.io/heroic

dev.mysql.com/doc

Developer

Google

Spotify

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2010

2008

2014

1995

Current release

8.1, December 2018

8.4.0, April 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

AGPL, commercial license also available

commercial

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

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

Implementation language

Python

Java

C and C++

Server operating systems

Linux

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

specific XML type available, but no XML query functionality

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

standard, with numerous extensions

SQL-like query language (GQL)

yes

with proprietary extensions

APIs and other access methods

CLI Client
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
Go
Java
JavaScript (Node.js)
PHP
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

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

using Google App Engine

yes

proprietary syntax

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

other methods possible by using 3rd party extensions

Multi-source replication using Paxos

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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,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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.