DBMS > Axibase vs. Google BigQuery vs. Heroic vs. HyperSQL

System Properties Comparison Axibase vs. Google BigQuery vs. Heroic vs. HyperSQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

Large scale data warehouse service with append-only tables

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Primary database model

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

Score	0.32
Rank	#288	Overall
	#25	Time Series DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	3.90
Rank	#85	Overall
	#46	Relational DBMS

Website

axibase.com/docs/atsd/finance

cloud.google.com/bigquery

github.com/spotify/heroic

hsqldb.org

Technical documentation

cloud.google.com/bigquery/docs

spotify.github.io/heroic

hsqldb.org/web/hsqlDocsFrame.html

Developer

Axibase Corporation

Google

Spotify

Initial release

2013

2010

2014

2001

Current release

15585

2.7.2, June 2023

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

commercial

Open Source

Apache 2.0

Open Source

based on BSD license

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

Server operating systems

Linux

hosted

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

RESTful HTTP/JSON API

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

HTTP API

JDBC via HTTP
JDBC
ODBC

Supported programming languages

Go
Java
PHP
Python
R
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC
Java

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Java, SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

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)

fine grained access rights according to SQL-standard

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.