DBMS > Google BigQuery vs. HBase vs. Hypertable vs. IRONdb

System Properties Comparison Google BigQuery vs. HBase vs. Hypertable vs. IRONdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

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

Description

Large scale data warehouse service with append-only tables

Wide-column store based on Apache Hadoop and on concepts of BigTable

An open source BigTable implementation based on distributed file systems such as Hadoop

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

Primary database model

Relational DBMS

Wide column store

Time Series DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Website

cloud.google.com/bigquery

hbase.apache.org

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

Technical documentation

cloud.google.com/bigquery/docs

hbase.apache.org/book.html

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

Developer

Google

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Hypertable Inc.

Circonus LLC.

Initial release

2010

2008

2009

2017

Current release

2.3.4, January 2021

0.9.8.11, March 2016

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

GNU version 3. 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

Java

C++

C and C++

Server operating systems

hosted

Linux
Unix
Windows

using Cygwin

Linux
OS X
Windows

an inofficial Windows port is available

Linux

Data scheme

yes

schema-free, schema definition possible

schema-free

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

restricted

only exact value or prefix value scans

SQL

Support of SQL

yes

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

APIs and other access methods

RESTful HTTP/JSON API

Java API
RESTful HTTP API
Thrift

C++ API
Thrift

HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Groovy
Java
PHP
Python
Scala

C++
Java
Perl
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

Coprocessors in Java

yes, in Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Automatic, metric affinity per node

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor on file system level

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

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

Single row ACID (across millions of columns)

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.