DBMS > Apache Drill vs. CockroachDB vs. Google BigQuery vs. IRONdb

System Properties Comparison Apache Drill vs. CockroachDB vs. Google BigQuery vs. IRONdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Primary database model

Document store
Relational DBMS

Relational DBMS

Time Series DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Website

drill.apache.org

www.cockroachlabs.com

cloud.google.com/bigquery

www.circonus.com/solutions/time-series-database/

Technical documentation

drill.apache.org/docs

www.cockroachlabs.com/docs

cloud.google.com/bigquery/docs

docs.circonus.com/irondb/category/getting-started

Developer

Apache Software Foundation

Cockroach Labs

Google

Circonus LLC.

Initial release

2012

2015

2010

2017

Current release

1.20.3, January 2023

24.1.0, May 2024

V0.10.20, January 2018

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0, commercial license available

commercial

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 and C++

Server operating systems

Linux
OS X
Windows

Linux
macOS
Windows

hosted

Linux

Data scheme

schema-free

dynamic schema

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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.

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes, wire compatible with PostgreSQL

yes

SQL-like query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

RESTful HTTP/JSON API

HTTP API

Supported programming languages

C++

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes, in Lua

Triggers

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

Automatic, metric affinity per node

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

configurable replication factor, datacenter aware

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

User concepts

Access control

Depending on the underlying data source

Role-based access control

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

Google Cloud Identity & Access Management (IAM)

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.