DBMS > Apache Impala vs. BigchainDB vs. CockroachDB vs. Google BigQuery vs. MySQL

System Properties Comparison Apache Impala vs. BigchainDB vs. CockroachDB vs. Google BigQuery vs. MySQL

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

Large scale data warehouse service with append-only tables

Widely used open source RDBMS

Primary database model

Relational DBMS

Document store

Relational DBMS

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	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	0.76
Rank	#216	Overall
	#36	Document stores

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

impala.apache.org

www.bigchaindb.com

www.cockroachlabs.com

cloud.google.com/bigquery

www.mysql.com

Technical documentation

impala.apache.org/impala-docs.html

bigchaindb.readthedocs.io/en/latest

www.cockroachlabs.com/docs

cloud.google.com/bigquery/docs

dev.mysql.com/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Cockroach Labs

Google

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

2016

2015

2010

1995

Current release

4.1.0, June 2022

24.1.0, May 2024

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

AGPL v3

Open Source

Apache 2.0, commercial license available

commercial

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.

Implementation language

C++

Python

C and C++

Server operating systems

Linux

Linux
macOS
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

dynamic schema

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

SQL-like DML and DDL statements

yes, wire compatible with PostgreSQL

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

CLI Client
RESTful HTTP API

JDBC

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

Go
Haskell
Java
JavaScript
Python
Ruby

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

.Net
Java
JavaScript
Objective-C
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

yes

user defined functions and integration of map-reduce

user defined functions

in JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using RAFT

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

Since BigQuery is designed for querying 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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

yes

Role-based access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & 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.